From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22973 invoked by alias); 3 Nov 2005 15:59:33 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 22955 invoked by uid 22791); 3 Nov 2005 15:59:30 -0000 Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Thu, 03 Nov 2005 15:59:30 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1EXhUu-0000Aw-56; Thu, 03 Nov 2005 10:59:28 -0500 Date: Thu, 03 Nov 2005 15:59:00 -0000 From: Daniel Jacobowitz To: Frank Meerkoetter Cc: gdb@sourceware.org Subject: Re: multithreaded programs on arm-linux Message-ID: <20051103155928.GA630@nevyn.them.org> Mail-Followup-To: Frank Meerkoetter , gdb@sourceware.org References: <20051102134303.GA26674@nevyn.them.org> <20051102143909.GA27932@nevyn.them.org> <20051102165558.mg4g0d5htl8ockco@admin.betaversion.net> <20051102164925.GA31801@nevyn.them.org> <20051103093306.qyr5bz57icqo04ck@admin.betaversion.net> <20051103135617.GA29302@nevyn.them.org> <20051103160009.8sy1s7ydxhwok0ww@admin.betaversion.net> <20051103150707.GA31256@nevyn.them.org> <20051103165107.69fo0r6r2li8csws@admin.betaversion.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051103165107.69fo0r6r2li8csws@admin.betaversion.net> User-Agent: Mutt/1.5.8i X-SW-Source: 2005-11/txt/msg00065.txt.bz2 On Thu, Nov 03, 2005 at 04:51:07PM +0100, Frank Meerkoetter wrote: > Quoting Daniel Jacobowitz : > [...] > >>I'm not using the gdbserver but rather running the gdb on > >>the target. The reason is that i didn't managed to > >>remote debug a program which is dynamically linked. > >> > >>I assume gdb is linked against libthread_db.so > > > >GDB uses dlopen to get at libthread_db.so. Does it do that? Does > >initialization fail? > > thread_db_load() which contains the dlopen() call is successfull run. > The end of thread_db_load() is reached and 1 is returned. > > >You'll need to attach a debugger to gdb and look at thread_db_init. > >The first call will generally fail but a later one should succeed. > > frank@linux:~/gdb/gdb-6.3> global thread_db_init > gdb/gdbserver/thread-db.c > gdb/thread-db.c > > thread_db_init of the gdbserver could fail but not thread_db_init > of the gdb. Try thread_db_new_objfile. -- Daniel Jacobowitz CodeSourcery, LLC