From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31727 invoked by alias); 12 Mar 2007 22:09:59 -0000 Received: (qmail 31719 invoked by uid 22791); 12 Mar 2007 22:09:58 -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 22:09:51 +0000 Received: from localhost (localhost [127.0.0.1]) by filtered-nile.gnat.com (Postfix) with ESMTP id 77B1648D08A; Mon, 12 Mar 2007 18:09:15 -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 18215-02; Mon, 12 Mar 2007 17:09:15 -0500 (EST) Received: from takamaka.act-europe.fr (unknown [70.71.0.212]) by nile.gnat.com (Postfix) with ESMTP id DCB8C48D06E; Mon, 12 Mar 2007 18:09:14 -0400 (EDT) Received: by takamaka.act-europe.fr (Postfix, from userid 1000) id 46F8BE7B38; Mon, 12 Mar 2007 15:09:49 -0700 (PDT) Date: Mon, 12 Mar 2007 22:09:00 -0000 From: Joel Brobecker To: Eli Zaretskii Cc: gdb@sourceware.org Subject: Re: [sparc-solaris] unexpected warning when starting program Message-ID: <20070312220949.GP14401@adacore.com> References: <20070312051646.GI14401@adacore.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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/msg00177.txt.bz2 > > I am not sure how to fix it either. On solaris 2.8 and 2.9, the two > > files are identical but distinct - one is not a link to the other. > > On solaris 2.10, however, one is a link of the other, so we could > > presumably check the fullpath instead of doing a direct name comparison. > > But that would be pretty expensive for just one type of host, no? > > String comparisons is the wrong thing to do when the issue is file > equality. This mostly works only by chance. We should implement a > smarter FILENAME_CMP, IMHO. I completely agree, and I was planning on using FILENAME_CMP in any solution we might come up with. But we also have to realize that unless FILENAME_CMP also knows that on solaris /lib/ld.so is the same as /usr/lib/ld.so (which is a possibility), then this isn't going to make this particular warning go away... -- Joel