This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: GDB locks up -- Cannot find new threads: generic error
- From: David Lecomber <david at allinea dot com>
- To: Andreas Schwab <schwab at suse dot de>
- Cc: gdb <gdb at sources dot redhat dot com>
- Date: Tue, 03 May 2005 15:21:25 +0100
- Subject: Re: GDB locks up -- Cannot find new threads: generic error
- References: <1114627357.31720.81.camel@cpc4-oxfd5-5-0-cust111.oxfd.cable.ntl.com> <20050427190108.GA28978@nevyn.them.org> <jefyxbvnwd.fsf@sykes.suse.de>
> >> The system is:
> >> kernel-2.4.21-27.EL
> >> glibc-2.3.2-95.30
> >
> > At a guess, your kernel is buggered. You really should never see that
> > warning. The unexpected signal is SIGCHLD; your kernel has accepted
> > the SETOPTIONS but obviously failed to stop when the test thread
> > vforked.
>
> I think that can happen when the 32 bit ptrace emulation is incomplete,
> especially if PTRACE_GETEVENTMSG is not properly emulated. That should be
> fixed in recent (< 9 months) kernels.
Hello Andreas,
I can reproduce this on a SuSE Opteron machine - running 2.6.8-24.13 -
and 2.6.8 came out 13th August (?). How - other than brokenness - can I
test if this PTRACE_GETEVENTMSG is the problem?
Regards
David