From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-9323-listarch-gdb=sourceware.cygnus.com@sources.redhat.com>
Received: (qmail 32517 invoked by alias); 25 Jun 2002 08:48:17 -0000
Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb/>
List-Post: <mailto:gdb@sources.redhat.com>
List-Help: <mailto:gdb-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-owner@sources.redhat.com
Received: (qmail 32484 invoked from network); 25 Jun 2002 08:48:13 -0000
Received: from unknown (HELO pc4) (80.192.14.187)
  by sources.redhat.com with SMTP; 25 Jun 2002 08:48:13 -0000
Received: from jcownie by etnus.com with esmtp (MasqMail 0.1.16) id
 17Mlzg-0If-00 for gdb@sources.redhat.com; Tue, 25 Jun 2002 09:48:12
 +0100
To: gdb@sources.redhat.com
Subject: Re: GDB support for thread-local storage
In-reply-to: Your message of "24 Jun 2002 21:04:00 -0000."
             <1024952640.13693.ezmlm@sources.redhat.com> 
Date: Tue, 25 Jun 2002 01:48:00 -0000
From: James Cownie <jcownie@etnus.com>
Message-ID: <17Mlzg-0If-00@etnus.com>
X-SW-Source: 2002-06/txt/msg00237.txt.bz2

> > 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.

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.

-- Jim 

James Cownie	<jcownie@etnus.com>
Etnus, LLC.     +44 117 9071438
http://www.etnus.com