From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20791 invoked by alias); 3 May 2005 14:25:24 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 20616 invoked from network); 3 May 2005 14:25:09 -0000 Received: from unknown (HELO webmail.streamline-computing.com) (82.133.39.164) by sourceware.org with SMTP; 3 May 2005 14:25:09 -0000 Received: from [82.133.39.162] (helo=delmo.priv.wark.uk.streamline-computing.com) by webmail.streamline-computing.com with asmtp (Exim 3.35 #1 (Debian)) id 1DSyM9-00071H-00; Tue, 03 May 2005 15:26:37 +0100 Subject: Re: GDB locks up -- Cannot find new threads: generic error From: David Lecomber To: Andreas Schwab Cc: gdb In-Reply-To: References: <1114627357.31720.81.camel@cpc4-oxfd5-5-0-cust111.oxfd.cable.ntl.com> <20050427190108.GA28978@nevyn.them.org> Content-Type: text/plain Date: Tue, 03 May 2005 14:25:00 -0000 Message-Id: <1115130086.1638.27.camel@delmo.priv.wark.uk.streamline-computing.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-SW-Source: 2005-05/txt/msg00032.txt.bz2 > >> 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