Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb@sourceware.org
Subject: Re: [sparc-solaris] unexpected warning when starting program
Date: Mon, 12 Mar 2007 22:09:00 -0000	[thread overview]
Message-ID: <20070312220949.GP14401@adacore.com> (raw)
In-Reply-To: <ur6rup1a4.fsf@gnu.org>

> > 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


  reply	other threads:[~2007-03-12 22:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-12  5:16 Joel Brobecker
2007-03-12 11:07 ` Daniel Jacobowitz
2007-03-12 17:17   ` Joel Brobecker
2007-03-20  8:39   ` Denis PILAT
2007-04-10 21:40     ` Daniel Jacobowitz
2007-04-17 14:51       ` Denis PILAT
2007-03-12 22:03 ` Eli Zaretskii
2007-03-12 22:09   ` Joel Brobecker [this message]
2007-04-10 21:35 ` Daniel Jacobowitz
2007-04-11  6:45   ` Joel Brobecker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070312220949.GP14401@adacore.com \
    --to=brobecker@adacore.com \
    --cc=eliz@gnu.org \
    --cc=gdb@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox