From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21736 invoked by alias); 13 Mar 2002 17:50:20 -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 21643 invoked from network); 13 Mar 2002 17:50:17 -0000 Received: from unknown (HELO nevyn.them.org) (128.2.145.6) by sources.redhat.com with SMTP; 13 Mar 2002 17:50:17 -0000 Received: from drow by nevyn.them.org with local (Exim 3.35 #1 (Debian)) id 16lCsQ-0003m3-00; Wed, 13 Mar 2002 12:49:26 -0500 Date: Wed, 13 Mar 2002 09:50:00 -0000 From: Daniel Jacobowitz To: Miah Gregory Cc: gdb@sources.redhat.com Subject: Re: gdb/threading under arm-linux Message-ID: <20020313124926.A14483@nevyn.them.org> Mail-Followup-To: Miah Gregory , gdb@sources.redhat.com References: <908b78124b.miah@picsel.com> <20020305103521.A27860@nevyn.them.org> <20020306110033.A14410@nevyn.them.org> <20020313120947.A12715@nevyn.them.org> <7f89ad164b.miah@picsel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7f89ad164b.miah@picsel.com> User-Agent: Mutt/1.3.23i X-SW-Source: 2002-03/txt/msg00120.txt.bz2 On Wed, Mar 13, 2002 at 05:43:08PM +0000, Miah Gregory wrote: > In message <20020313120947.A12715@nevyn.them.org> > Daniel Jacobowitz wrote: > > > On Wed, Mar 13, 2002 at 01:11:57PM +0000, Miah Gregory wrote: > > > > In message <20020306110033.A14410@nevyn.them.org> > > > Daniel Jacobowitz wrote: > > > > > You almost certainly do not have libthread_db.so.1 in /lib. > > > > You need that to debug threads. > > > > Ok, I managed to build enough of libc 2.2.3 in order to get the > > > required libthread_db.so.1 library, and I then installed that in /lib. > > > > With the 20020305 snapshot, I get all the same problems. Is there a > > > simple way to find out whether gdb is trying to use that library? > > > I recommend running gdb within gdb, and breakpointing on > > thread_db_load. > > Sounds reasonable. > > When I do that, gdb makes its way through thread_db_init to the final > 'return 1;', which I assume from the code means that it opened and > initialised libthread_db correctly. > > Anything else I can break on? Which function is called when a new thread is > created? > > Running gdb from start to finish, these are the only functions within > thread_db.c that are called, in order: > > thread_db_load > init_thread_db_ops > thread_db_init > thread_db_new_objfile (objfile = 0x0000000) > thread_db_new_objfile (objfile = 0x2207e18) Might want to step through thread_db_new_objfile. Is something causing it to turn off thread_db? Wait, from that pattern of calls it looks like you are using a statically linked binary. Try using a dynamically linked binary, and I'll take another look at HJ's patch to fix the static case :) -- Daniel Jacobowitz Carnegie Mellon University MontaVista Software Debian GNU/Linux Developer