From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25377 invoked by alias); 21 Feb 2003 19:14:35 -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 25369 invoked from network); 21 Feb 2003 19:14:35 -0000 Received: from unknown (HELO hub.ott.qnx.com) (209.226.137.76) by 172.16.49.205 with SMTP; 21 Feb 2003 19:14:35 -0000 Received: from smtp.ott.qnx.com (smtp.ott.qnx.com [10.0.2.158]) by hub.ott.qnx.com (8.9.3/8.9.3) with ESMTP id OAA18920; Fri, 21 Feb 2003 14:02:45 -0500 Received: from catdog ([10.4.2.2]) by smtp.ott.qnx.com (8.8.8/8.6.12) with SMTP id OAA18643; Fri, 21 Feb 2003 14:14:34 -0500 Message-ID: <02b201c2d9dd$741f8de0$0202040a@catdog> From: "Kris Warkentin" To: "Kris Warkentin" , "Daniel Jacobowitz" , "Paul Koning" Cc: , , "Colin Burgess" References: <0db801c2d914$78f80a50$0202040a@catdog> <1030220193301.ZM10611@localhost.localdomain> <20030220194049.GA19653@nevyn.them.org> <001301c2d918$894ef1d0$0202040a@catdog> <20030220194852.GA20424@nevyn.them.org> <002701c2d919$d07edce0$0202040a@catdog> <1030220195833.ZM10783@localhost.localdomain> <15957.17196.501000.893848@gargle.gargle.HOWL> <20030220201032.GA21694@nevyn.them.org> <00e001c2d9be$616ca940$0202040a@catdog> <023401c2d9d7$5441ce30$0202040a@catdog> Subject: Re: [Proposal] GDB honouring RPATH in binaries. Date: Fri, 21 Feb 2003 19:14:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-SW-Source: 2003-02/txt/msg00477.txt.bz2 > So, I have two potential solutions: > > One: We could add something like 'vendor-solib-search-path' which could be > searched so that solib-search-path can be left for the user. Then vendors > can just initialize v-s-s-p and users don't have to worry. > > Two: provide a mechanism to append strings to gdb variables such as > solib-search-path which might be useful in other situations. A really nice > implementation would be some form of variable expansion, ie: > > set solib-search-path $solib-search-path:/home/foo > Ooh ooh....number 3 just came to mind. In solib_open(), we go through a bunch of, "Lib not found yet? Okay, try this. Still not found? Okay, try this". We could just make a target_ops solib_open_hook that returns a fd to the lib in some vendor/target defined way. Then, in solib_open(), we just check to see if the hook is there and try to open the lib with that. This would work really well because then we can adjust on the fly to endian issues, etc. ie. $QNX_TARGET/armbe or armle. Kris