From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24297 invoked by alias); 3 May 2005 20:55:39 -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 23883 invoked from network); 3 May 2005 20:55:25 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sourceware.org with SMTP; 3 May 2005 20:55:25 -0000 Received: from drow by nevyn.them.org with local (Exim 4.50 #1 (Debian)) id 1DT4QM-00020e-M6; Tue, 03 May 2005 16:55:22 -0400 Date: Tue, 03 May 2005 20:55:00 -0000 From: Daniel Jacobowitz To: David Lecomber Cc: Andreas Schwab , gdb Subject: Re: GDB locks up -- Cannot find new threads: generic error Message-ID: <20050503205522.GA7648@nevyn.them.org> Mail-Followup-To: David Lecomber , Andreas Schwab , gdb References: <1114627357.31720.81.camel@cpc4-oxfd5-5-0-cust111.oxfd.cable.ntl.com> <20050427190108.GA28978@nevyn.them.org> <1115130086.1638.27.camel@delmo.priv.wark.uk.streamline-computing.com> <20050503144844.GA24721@nevyn.them.org> <1115153724.10279.13.camel@cpc4-oxfd5-5-0-cust111.oxfd.cable.ntl.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1115153724.10279.13.camel@cpc4-oxfd5-5-0-cust111.oxfd.cable.ntl.com> User-Agent: Mutt/1.5.8i X-SW-Source: 2005-05/txt/msg00040.txt.bz2 On Tue, May 03, 2005 at 09:55:23PM +0100, David Lecomber wrote: > > Sorry Dan, it didn't work: > > (gdb) b main > Breakpoint 1 at 0x80484dd: file foo.c, line 15. > (gdb) r > Starting program: /users/david/a.out > warning: linux_test_for_tracefork: Needed to use long, but second half > was clobbered Well, that's something - Andreas was right about your kernel having this broken. The patch may be a good idea anyway to prevent really odd stack corruption bugs. > Failed to read a valid object file image from memory. > [Thread debugging using libthread_db enabled] > Error while reading shared library symbols: > Cannot find new threads: generic error > > > followed by hanging.. I will need more information to help you. Useful things: strace of gdb, backtrace at the time of the hang, whatever else you can think of to try... -- Daniel Jacobowitz CodeSourcery, LLC