linux-kernel - Re: 2.6.25.3: su gets stuck for root

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080518185104.0a539f25@core>
Date:	Sun, 18 May 2008 18:51:04 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Harald Dunkel <harald.dunkel@...nline.de>
Cc:	Vegard Nossum <vegard.nossum@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: 2.6.25.3: su gets stuck for root

> This GDB was configured as "x86_64-linux-gnu"...
> Attaching to program: /var/tmp/coreutils-6.10/coreutils-6.10/src/stty, process 26465
> /tmp/buildd/gdb-6.8/gdb/linux-nat.c:988: internal-error: linux_nat_attach: Assertion `pid == GET_PID (inferior_ptid) && WIFSTOPPED (status) && WSTOPSIG (status) == SIGSTOP' failed.
> A problem internal to GDB has been detected,

So your gdb is broken, your stty is doign stuff nobody else seems to be
seeing ? My first thought is to suspect the distro/source as I've still
had no other equivalent reports and given the gdb spew.

I'll have a dig further however as the GDB spew itself might actually be
a useful clue. Not sure I can do much without a proper trace however (if
gdb is borked on your box is strace giving sane reports ?)

Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/