From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26403 invoked by alias); 5 May 2009 03:38:46 -0000 Received: (qmail 26395 invoked by uid 22791); 5 May 2009 03:38:45 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 05 May 2009 03:38:40 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id F10D32BABA4; Mon, 4 May 2009 23:38:38 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 6pBrLkDmpUgI; Mon, 4 May 2009 23:38:38 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 9CAFA2BAB99; Mon, 4 May 2009 23:38:38 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id 63923F5900; Mon, 4 May 2009 20:38:35 -0700 (PDT) Date: Tue, 05 May 2009 03:38:00 -0000 From: Joel Brobecker To: Hui Zhu Cc: Paul Pluzhnikov , tromey@redhat.com, Thiago Jung Bauermann , gdb-patches ml , Eli Zaretskii Subject: Re: [patch][rfc] Allow GDB to search for the right libthread_db.so.1 Message-ID: <20090505033835.GH10734@adacore.com> References: <8ac60eac0904221810x24763ecaj4a888927b766e7f7@mail.gmail.com> <8ac60eac0904230001w1afd9179wcb76e1cfd7f3f386@mail.gmail.com> <8ac60eac0904291330m78b43c47p1cc9b8379e31e923@mail.gmail.com> <20090430185551.GB10734@adacore.com> <8ac60eac0905032031i401dbe2eke5608b67d13d8732@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2009-05/txt/msg00075.txt.bz2 > Actually, I think libthread_db_search_path is cool function, not > because it can't be substituted, but because it can make gdb more > powerful. > But if after we have this function, we still need: > > even in this case, it's easy to create a symbolic link in a user > > area, and update the path to point to that directory. > I don't think it is very well. > > Sorry for my words is directly. The problem is that you don't necessarily have root priviledges to do the move that you describe. You might also want to *not* disturb the rest of the system by moving out the thread_db lib on the host just to put the one that was used on the target. On the other hand, my understanding is that it's unlikely that this library will have a different name; so the feature of being able to specify the name in the search path is only hypothetical. And even if it happens, it's easy to create a symbolic link in an area that you have write access to (say, your home directory), and then point the search path to link. That's why we're suggesting that it's not worth allowing files in the path. -- Joel