From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org, dj@redhat.com,
ktietz70@googlemail.com, binutils@sourceware.org,
gcc-patches@gcc.gnu.org
Subject: Re: [patch libiberty include]: Add additional helper functions for directory-separator searching
Date: Wed, 09 Mar 2011 13:36:00 -0000 [thread overview]
Message-ID: <83lj0opgav.fsf@gnu.org> (raw)
In-Reply-To: <201103091258.38655.pedro@codesourcery.com>
> From: Pedro Alves <pedro@codesourcery.com>
> Date: Wed, 9 Mar 2011 12:58:38 +0000
> Cc: gdb-patches@sourceware.org,
> dj@redhat.com,
> ktietz70@googlemail.com,
> binutils@sourceware.org,
> gcc-patches@gcc.gnu.org
>
> > > The one's left are: 1 in a linux-native only file (never cares
> > > for other filesystem semantics), and a couple in the coff and
> > > mdebug readers. The latter could be rewritten in terms of
> > > lbasename, but I'm not sure whether gcc outputs a literal '/' in
> > > that case even when building on mingw. If so, and we changed them,
> > > we'd be breaking reading these files on Windows
> >
> > Sorry, I don't understand how would that break on Windows. Could you
> > elaborate? And what "couple of coff and mdebug readers" did you have
> > in mind?
>
> Sorry, in the hurry, I had a (another) brain cramp. Wouldn't break.
> Still it'd be useless to change this _if_ gcc hardcodes '/'. Dunno
> whether it does.
At least on MinGW, GCC simply uses whatever was passed on the command
line. I tested that by compiling the same source file, passing it to
GCC with different flavors of slashes, including mixed ones. Then in
GDB I typed "info sources" and saw the source file with exactly the
same flavor of slashes as what I typed on the GCC command line.
Funnily enough, when the file name given to GCC includes at least one
backslash, "info sources" shows the same file twice, like this:
(gdb) info sources
Source files for which symbols have been read in:
Source files for which symbols will be read in on demand:
d:/usr/eli/data/dbw.c, d:\usr\eli/data\dbw.c
This is with GDB 7.2 and GCC 3.4.2. That means we compare files with
strcmp/strcasecmp somewhere, and don't know that / and \ are
equivalent here. Or maybe it's a bug in the ancient version of GCC I
use.
next prev parent reply other threads:[~2011-03-09 13:36 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 10:56 Kai Tietz
2011-03-08 11:12 ` Eli Zaretskii
2011-03-08 11:25 ` Kai Tietz
2011-03-08 11:53 ` Eli Zaretskii
2011-03-08 12:01 ` Kai Tietz
2011-03-08 12:43 ` Pedro Alves
2011-03-08 12:48 ` Kai Tietz
2011-03-08 13:33 ` Pedro Alves
2011-03-08 13:37 ` Kai Tietz
2011-03-08 18:39 ` Eli Zaretskii
2011-03-08 18:50 ` Pedro Alves
2011-03-08 18:51 ` Kai Tietz
2011-03-08 19:54 ` Eli Zaretskii
[not found] ` <E1Pwupb-0001ns-M8__47566.5626036518$1299582745$gmane$org@fencepost.gnu.org>
2011-03-08 11:55 ` Andreas Schwab
2011-03-08 15:11 ` Kai Tietz
2011-03-08 15:30 ` Kai Tietz
2011-03-08 18:37 ` Eli Zaretskii
2011-03-08 19:41 ` DJ Delorie
2011-03-08 19:59 ` Eli Zaretskii
2011-03-08 22:38 ` Pedro Alves
2011-03-09 5:29 ` Eli Zaretskii
2011-03-09 11:46 ` Pedro Alves
2011-03-09 12:35 ` Eli Zaretskii
2011-03-09 12:58 ` Pedro Alves
2011-03-09 13:36 ` Eli Zaretskii [this message]
2011-03-12 16:40 ` Kai Tietz
2011-03-09 14:37 ` Build regression [Re: [patch libiberty include]: Add additional helper functions for directory-separator searching] Jan Kratochvil
2011-03-09 15:02 ` Pedro Alves
2011-03-09 15:08 ` Jan Kratochvil
2011-03-12 16:44 ` [patch libiberty include]: Add additional helper functions for directory-separator searching Kai Tietz
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=83lj0opgav.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=binutils@sourceware.org \
--cc=dj@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=ktietz70@googlemail.com \
--cc=pedro@codesourcery.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).