This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
Re: gdb/2238: assertion failure in linux_nat_attach() when attaching to a hung Xorg instance
- From: Daniel Jacobowitz <drow at false dot org>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 7 Mar 2007 16:48:01 -0000
- Subject: Re: gdb/2238: assertion failure in linux_nat_attach() when attaching to a hung Xorg instance
- Reply-to: Daniel Jacobowitz <drow at false dot org>
The following reply was made to PR gdb/2238; it has been noted by GNATS.
From: Daniel Jacobowitz <drow@false.org>
To: bernie@codewiz.org
Cc: gdb-gnats@sources.redhat.com
Subject: Re: gdb/2238: assertion failure in linux_nat_attach() when attaching to a hung Xorg instance
Date: Wed, 7 Mar 2007 11:42:11 -0500
On Wed, Mar 07, 2007 at 04:30:32PM -0000, bernie@codewiz.org wrote:
> GNU gdb Red Hat Linux (6.6-4.fc7rh)
Do you get the same results if you use an FSF GDB? I don't know if
any of the patches Red Hat applies affect this.
> [...]
> Attaching to program: /usr/local/fdo/bin/Xorg, process 29958
> ../../gdb/linux-nat.c:1085: internal-error: linux_nat_attach: Assertion `pid == GET_PID (inferior_ptid) && WIFSTOPPED (status) && (WSTOPSIG (status) == SIGSTOP || WSTOPSIG (status) == 0)' failed.
> A problem internal to GDB has been detected,
> further debugging may prove unreliable.
>
> Maybe Xorg also does something weird with signal masks. This is the stack backtrace I get if I rebuild gdb
> without the assertion:
Could you check which bit of the assertion failed, and how so?
Probably the wait status is something unusual.
--
Daniel Jacobowitz
CodeSourcery