From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24222 invoked by alias); 3 Aug 2005 13:38:27 -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 23922 invoked by uid 22791); 3 Aug 2005 13:38:21 -0000 Received: from sadr.equallogic.com (HELO sadr.equallogic.com) (66.155.203.134) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Wed, 03 Aug 2005 13:38:21 +0000 Received: from sadr.equallogic.com (localhost.localdomain [127.0.0.1]) by sadr.equallogic.com (8.12.8/8.12.8) with ESMTP id j73DcJZZ001607 for ; Wed, 3 Aug 2005 09:38:19 -0400 Received: from M31.equallogic.com (M31.equallogic.com [172.16.1.31]) by sadr.equallogic.com (8.12.8/8.12.8) with SMTP id j73DcJNd001602 for ; Wed, 3 Aug 2005 09:38:19 -0400 Received: from pkoning.equallogic.com ([172.16.1.163]) by M31.equallogic.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 3 Aug 2005 09:38:19 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17136.51402.673936.895045@gargle.gargle.HOWL> Date: Wed, 03 Aug 2005 13:38:00 -0000 From: Paul Koning To: gdb@sources.redhat.com Subject: solib search algorithm for cross-gdb X-SW-Source: 2005-08/txt/msg00016.txt.bz2 Currently, the shared library search in solib.c first tries to use the shared lib filename as given (if solib-absolute-prefix isn't set). That's exactly right for a native gdb, but it is in general the wrong answer for a cross-gdb. If I'm debugging a mips box, or analyzing a mips corefile, resolving shared lib symbols from intel shared libs in my /usr/lib is the wrong thing. .gdbinit helps, but not everyone remembers to do this right every time. I was thinking about having the case of "use the filename exactly as supplied" in solib.c be used only in native gdb. That seems to require adding stuff in configure and config.in to tell a native from a cross build. I could submit this patch if it sounds like a good feature (otherwise I'll probably keep it as a private change). Comments? Better ways to do this? paul