Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Michael Snyder" <msnyder@sonic.net>
To: "Eli Zaretskii" <eliz@gnu.org>
Cc: <drow@false.org>, <gdb-patches@sourceware.org>
Subject: Re: [PATCH] symfile.c, find_separate_debug_file
Date: Fri, 03 Aug 2007 14:43:00 -0000	[thread overview]
Message-ID: <001301c7d5db$d5702880$677ba8c0@sonic.net> (raw)
In-Reply-To: <uy7gsbxzg.fsf@gnu.org>


----- Original Message ----- 
From: "Eli Zaretskii" <eliz@gnu.org>
To: "Michael Snyder" <msnyder@sonic.net>
Cc: <drow@false.org>; <gdb-patches@sourceware.org>
Sent: Friday, August 03, 2007 5:31 AM
Subject: Re: [PATCH] symfile.c, find_separate_debug_file


> > From: "Michael Snyder" <msnyder@sonic.net>
> > Cc: <gdb-patches@sourceware.org>
> > Date: Thu, 2 Aug 2007 21:36:27 -0700
> >
> > > > * symfile.c (find_separate_debug_file): While consing up a path,
> > > > don't stick in an extra DIR_SEPARATOR.
> > >
> > > That's right, use DIR_SEPARATOR :-)  IS_DIR_SEPARATOR in this case, I
> > > think?
> >
> > The existing code doesn't use it.
>
> Correction: the existing code appends "/" unconditionally, which is
> fine, since both Posix and non-Posix platforms support forward slashes
> in file names.
>
> But Daniel didn't mean that: he meant to use IS_DIR_SEPARATOR instead
> of literal comparison to '/' alone.  The existing code didn't test
> anything, so it didn't have to cope with this issue.

Yes, I understood exactly what Daniel meant.  I was saying,
the existing code uses the literal '/' instead of the symbolic
DIR_SEPARATOR.

I offered to have another go at the code and clean up the literals,
but as a separate patch to this one.



  reply	other threads:[~2007-08-03 14:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-03  1:14 msnyder
2007-08-03  1:30 ` Daniel Jacobowitz
2007-08-03  4:41   ` Michael Snyder
2007-08-03 11:40     ` Daniel Jacobowitz
2007-08-03 14:47       ` Michael Snyder
2007-08-03 15:00         ` Daniel Jacobowitz
2007-08-03 15:09           ` Michael Snyder
2007-08-03 15:19             ` Daniel Jacobowitz
2007-08-03 15:49           ` Andreas Schwab
2007-08-03 12:31     ` Eli Zaretskii
2007-08-03 14:43       ` Michael Snyder [this message]
2007-08-03 14:51         ` Daniel Jacobowitz
2007-08-03 17:12         ` Eli Zaretskii
2007-08-03 17:26           ` Michael Snyder
2007-08-03  5:54 ` Mark Kettenis
2007-08-03  7:15   ` Michael Snyder

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='001301c7d5db$d5702880$677ba8c0@sonic.net' \
    --to=msnyder@sonic.net \
    --cc=drow@false.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@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