From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12353 invoked by alias); 12 Mar 2007 17:17:16 -0000 Received: (qmail 12345 invoked by uid 22791); 12 Mar 2007 17:17:16 -0000 X-Spam-Check-By: sourceware.org Received: from nile.gnat.com (HELO nile.gnat.com) (205.232.38.5) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 12 Mar 2007 17:17:05 +0000 Received: from localhost (localhost [127.0.0.1]) by filtered-nile.gnat.com (Postfix) with ESMTP id C485B48CCA6 for ; Mon, 12 Mar 2007 13:17:03 -0400 (EDT) Received: from nile.gnat.com ([127.0.0.1]) by localhost (nile.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 18842-01 for ; Mon, 12 Mar 2007 12:17:03 -0500 (EST) Received: from takamaka.act-europe.fr (unknown [70.71.0.212]) by nile.gnat.com (Postfix) with ESMTP id 3913848CC5D for ; Mon, 12 Mar 2007 13:17:03 -0400 (EDT) Received: by takamaka.act-europe.fr (Postfix, from userid 1000) id 04DB8E7B38; Mon, 12 Mar 2007 10:17:37 -0700 (PDT) Date: Mon, 12 Mar 2007 17:17:00 -0000 From: Joel Brobecker To: gdb@sourceware.org Subject: Re: [sparc-solaris] unexpected warning when starting program Message-ID: <20070312171736.GL14401@adacore.com> References: <20070312051646.GI14401@adacore.com> <20070312110718.GB21646@caradoc.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070312110718.GB21646@caradoc.them.org> User-Agent: Mutt/1.4.2.2i Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-03/txt/msg00168.txt.bz2 > Maybe a gdbarch hook to override the name of the default dynamic > linker? That's really bizarre though. I agree it would be strange... Originally, I was thinking about extending the target_so_ops, to provide a routine that would tell us whether 2 SOs are identical or not. But I think this belongs more in the gdbarch vector: This is a property of the target. The way SOs work on solaris is not related to the fact that Solaris, for a reason that we ignore, has two copies of the same dynamic loader. It's really unfortunate to have to introduce an extra method just to compensate for that, but how does everyone feel if I add this new method which by default does what we do now (direct filename comparison), but on Solaris would also treat ld.so as an exception? -- Joel