From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18087 invoked by alias); 13 Sep 2006 03:47:59 -0000 Received: (qmail 18079 invoked by uid 22791); 13 Sep 2006 03:47:59 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Wed, 13 Sep 2006 03:47:55 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1GNLj6-0007Wd-Iq; Tue, 12 Sep 2006 23:47:52 -0400 Date: Wed, 13 Sep 2006 03:47:00 -0000 From: Daniel Jacobowitz To: Joel Brobecker Cc: gdb@sources.redhat.com Subject: Re: (linux/threads) Interesting side-effect of "auto-solib-add 0" Message-ID: <20060913034752.GA28904@nevyn.them.org> Mail-Followup-To: Joel Brobecker , gdb@sources.redhat.com References: <20060913002712.GF24293@adacore.com> <20060913003347.GA24280@nevyn.them.org> <20060913004720.GG24293@adacore.com> <20060913022113.GA26971@nevyn.them.org> <20060913034518.GH24293@adacore.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060913034518.GH24293@adacore.com> User-Agent: Mutt/1.5.13 (2006-08-11) X-IsSubscribed: yes 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 X-SW-Source: 2006-09/txt/msg00071.txt.bz2 On Tue, Sep 12, 2006 at 08:45:18PM -0700, Joel Brobecker wrote: > I have been thinking about that, but there were several little factors > that made me reconsider. The one that I didn't like the most was the > fact that the only way I could see to detect the pthread library being > loaded is by looking at its name. It doesn't feel very elegant to have > to search for "/libpthread.so" or somesuch in GDB. I don't know very > well how GNU/Linux distributions are made, but couldn't that library > be named libpthread-1.8.0.so, for instance, making its identification > harder? Well, if you wanted to be that precise about it, you could do it by SONAME. But I think matching libpthread wouldn't be that bad of a hack. > 2. Document the limitation (Eli also agreed with the idea) Let's go with this for now then. -- Daniel Jacobowitz CodeSourcery