From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15781 invoked by alias); 13 Mar 2002 17:44:17 -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 15391 invoked from network); 13 Mar 2002 17:44:03 -0000 Received: from unknown (HELO morbus.picsel.com) (212.137.21.218) by sources.redhat.com with SMTP; 13 Mar 2002 17:44:03 -0000 Received: by morbus.picsel.com (Postfix, from userid 1001) id CB6367FD9; Wed, 13 Mar 2002 17:44:02 +0000 (GMT) Received: from miahrpc (miahrpc.picsel.com [195.171.216.25]) by morbus.picsel.com (Postfix) with SMTP id 8EF7337FEB for ; Wed, 13 Mar 2002 17:44:01 +0000 (GMT) Date: Wed, 13 Mar 2002 09:44:00 -0000 From: Miah Gregory To: gdb@sources.redhat.com Subject: Re: gdb/threading under arm-linux Message-ID: <7f89ad164b.miah@picsel.com> References: <908b78124b.miah@picsel.com> <20020305103521.A27860@nevyn.them.org> <20020306110033.A14410@nevyn.them.org> <20020313120947.A12715@nevyn.them.org> In-Reply-To: <20020313120947.A12715@nevyn.them.org> X-Organization: Picsel Technologies Ltd User-Agent: Messenger-Pro/2.50c (MsgServe/1.50) (RISC-OS/4.02) POPstar/2.03 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by AMaViS snapshot-20010714 X-SW-Source: 2002-03/txt/msg00119.txt.bz2 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) I included the objfile argument here since it looked 'interesting'. :-) -- Miah Gregory