From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32066 invoked by alias); 19 Dec 2005 22:08:01 -0000 Received: (qmail 32051 invoked by uid 71); 19 Dec 2005 22:08:01 -0000 Date: Mon, 19 Dec 2005 22:08:00 -0000 Message-ID: <20051219220801.32050.qmail@sourceware.org> To: nobody@sources.redhat.com Cc: gdb-prs@sources.redhat.com, From: Daniel Jacobowitz Subject: Re: gdb/2054: can't start X server under gdb Reply-To: Daniel Jacobowitz Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-prs-owner@sourceware.org X-SW-Source: 2005-q4/txt/msg00140.txt.bz2 List-Id: The following reply was made to PR gdb/2054; it has been noted by GNATS. From: Daniel Jacobowitz 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