From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24149 invoked by alias); 3 Dec 2003 22:53:52 -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 24138 invoked from network); 3 Dec 2003 22:53:52 -0000 Received: from unknown (HELO hub.ott.qnx.com) (209.226.137.76) by sources.redhat.com with SMTP; 3 Dec 2003 22:53:52 -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 SAA27831; Wed, 3 Dec 2003 18:06:29 -0500 Received: from catdog ([10.4.2.2]) by smtp.ott.qnx.com (8.8.8/8.6.12) with SMTP id RAA14799; Wed, 3 Dec 2003 17:53:48 -0500 Message-ID: <071c01c3b9f0$744d04c0$0202040a@catdog> From: "Kris Warkentin" To: , , "Michael Elizabeth Chastain" References: <20031203223313.AD1B94B35A@berman.michael-chastain.com> Subject: Re: interesting solib-absolute-prefix problem Date: Wed, 03 Dec 2003 22:53: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.1165 X-SW-Source: 2003-12/txt/msg00073.txt.bz2 Actually, I just discovered a way to work around it in our back end TARGET_FIND_AND_OPEN_SOLIB. The fact that I KNOW we always have solib-absolute-prefix initialized means that I can cheat a bit. As far as setting it to "/", that doesn't work self-hosted because we need to specifically find something under /x86/usr/lib. Unfortunately I don't get to decide the layout, I just have to work with it. Either way, now I can keep the kludgey stuff in our own backend where it won't hurt anyone. Thanks for all the help. cheers, Kris ----- Original Message ----- From: "Michael Elizabeth Chastain" To: ; ; Sent: Wednesday, December 03, 2003 5:33 PM Subject: Re: interesting solib-absolute-prefix problem > Ummm, hit me with a clue-stick if I am missing the point, > but it looks like Kris's desire is to have solib-absolute-prefix="" > be a meaningful value, but gdb already uses that for something else. > And we don't want to get those semantics by accident. > > Can you kludge it by setting solib-absolute-prefix="/."? > > I agree with Kevin, I don't like kludges where gdb says > "might as well try this". The risk is that it will bogusly > succeed on some other system. > > Michael C >