From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26882 invoked by alias); 25 Jun 2002 15:05:10 -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 26874 invoked from network); 25 Jun 2002 15:05:09 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by sources.redhat.com with SMTP; 25 Jun 2002 15:05:09 -0000 Received: from cs2876-108.austin.rr.com ([24.28.76.108] helo=branoic) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 17MrsP-0001HK-00; Tue, 25 Jun 2002 10:05:05 -0500 Received: from drow by branoic with local (Exim 3.35 #1 (Debian)) id 17Mrrv-0004Ff-00; Tue, 25 Jun 2002 11:04:35 -0400 Date: Tue, 25 Jun 2002 08:05:00 -0000 From: Daniel Jacobowitz To: James Cownie Cc: gdb@sources.redhat.com Subject: Re: GDB support for thread-local storage Message-ID: <20020625150435.GB16178@branoic.them.org> Mail-Followup-To: James Cownie , gdb@sources.redhat.com References: <1024952640.13693.ezmlm@sources.redhat.com> <17Mlzg-0If-00@etnus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <17Mlzg-0If-00@etnus.com> User-Agent: Mutt/1.3.28i X-SW-Source: 2002-06/txt/msg00242.txt.bz2 On Tue, Jun 25, 2002 at 09:48:12AM +0100, James Cownie wrote: > > > But what is stopping us picking up that code, compiling it on the host > > > (not target), and then using it in GDB? > > > > Version skew primarily. > > Can you not choose the right version of libthread_db at runtime based > on the version of linuxthreads and dlopen it in gdb ? > > Ideally there'd be some version information in the thread library code > which gdb could extract in a specified manner, and then a convention > about how that maps to a the name of a suitable .so version of > libthread_db. But there isn't this version information. We could probably detect the glibc version number, but these are internal structures, not interfaces; detecting when they have changed is quite hard. > This lets you > > 1) use libthread_db inside gdb on the host machine > 2) keep gdb insulated from the version dependency on the thread > library. Nope. We'd have to be the ones writing such a thread_db; there is no version that can run on the host machine at present. -- Daniel Jacobowitz Carnegie Mellon University MontaVista Software Debian GNU/Linux Developer