This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: gdb/2054: can't start X server under gdb


The following reply was made to PR gdb/2054; it has been noted by GNATS.

From: Daniel Jacobowitz <drow@false.org>
To: ajackson@redhat.com
Cc: gdb-gnats@sources.redhat.com
Subject: Re: gdb/2054: can't start X server under gdb
Date: Mon, 19 Dec 2005 17:05:36 -0500

 On Mon, Dec 19, 2005 at 09:53:34PM -0000, ajackson@redhat.com wrote:
 > Attempting to run X (6.9RC4, but happens with earlier versions too) makes gdb flip out:
 > 
 > (gdb) run -ac -verbose -noreset :0
 > ...
 > (II) XINPUT: Adding extended input device "Keyboard1" (type: KEYBOARD)
 > (II) XINPUT: Adding extended input device "Mouse1" (type: MOUSE)
 > linux-nat.c:512: internal-error: wait returned unexpected status 0x4057f
 > A problem internal to GDB has been detected,
 > further debugging may prove unreliable.
 > Quit this debugging session? (y or n)     
 
 Huh - that (0x4057f) is SIGTRAP | (PTRACE_EVENT_EXEC << 16).  GDB shouldn't
 be receiving PTRACE_EVENT_EXEC notification.  Is this an unmodified
 kernel.org kernel?  Did X exec?
 
 Attaching the output of GDB if you "set debug lin-lwp 1" before "run"
 might shed some light on it.
 
 -- 
 Daniel Jacobowitz
 CodeSourcery, LLC


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]