From: Gary Benson <gbenson@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org, cedric.buissart@gmail.com
Subject: Re: [PATCH 1/5] Introduce build_debug_file_name
Date: Thu, 18 Jun 2015 10:55:00 -0000 [thread overview]
Message-ID: <20150618105528.GA2644@blade.nx> (raw)
In-Reply-To: <83a8vymgmg.fsf@gnu.org>
Eli Zaretskii wrote:
> > Date: Wed, 17 Jun 2015 10:47:34 +0100
> > From: Gary Benson <gbenson@redhat.com>
> > Cc: gdb-patches@sourceware.org, cedric.buissart@gmail.com
> >
> > For the case you mention nothing would be stripped (the "d" in
> > that path is !IS_DIR_SEPARATOR) so the filename components would
> > be concatenated verbatim, just as with the original code. The
> > resulting filename may not make sense, but it's not a regression.
>
> But won't we produce "d://foo/bar" as result?
No. build_debug_file_name strips both leading and trailing slashes.
The only ways to get a double slash from build_debug_file_name is to
pass one in in the middle of a string.
build_debug_file_name ("d:", "foo", "bar") -> "d:/foo/bar"
build_debug_file_name ("d:/", "/foo", "bar") -> "d:/foo/bar"
build_debug_file_name ("d:///", "///foo///", "bar") -> "d:/foo/bar"
but
build_debug_file_name("d://foo", "bar") -> "d://foo/bar"
> > I don't believe this series should be blocked unless it breaks
> > something that actually worked before.
>
> If a fix is very simple, why not make it?
I don't understand, what are you asking me to fix?
Thanks,
Gary
--
http://gbenson.net/
next prev parent reply other threads:[~2015-06-18 10:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-16 9:42 [PATCH 0/5] Separate debugfile improvements Gary Benson
2015-06-16 9:42 ` [PATCH 3/5] Update how find_separate_debug_file handles CANON_DIR argument Gary Benson
2015-07-01 11:13 ` Pedro Alves
2015-06-16 9:42 ` [PATCH 1/5] Introduce build_debug_file_name Gary Benson
2015-06-16 14:47 ` Eli Zaretskii
2015-06-17 9:47 ` Gary Benson
2015-06-17 16:42 ` Eli Zaretskii
2015-06-18 10:55 ` Gary Benson [this message]
2015-06-18 12:11 ` Eli Zaretskii
2015-06-19 8:32 ` Gary Benson
2015-07-01 11:05 ` Pedro Alves
2015-07-02 11:18 ` Gary Benson
2015-07-02 11:38 ` Pedro Alves
2015-07-02 13:53 ` Gary Benson
2015-07-25 16:20 ` Jan Kratochvil
2015-06-16 9:42 ` [PATCH 2/5] Pre-strip now-unnecessary trailing directory separators Gary Benson
2015-07-01 13:45 ` Pedro Alves
2015-06-16 9:48 ` [PATCH 4/5] Add "target:" filename handling to find_separate_debug_file Gary Benson
2015-07-01 13:35 ` Pedro Alves
2015-07-23 14:33 ` Gary Benson
2015-07-24 10:28 ` Gary Benson
2015-07-24 11:54 ` Gary Benson
2015-07-25 18:15 ` Jan Kratochvil
2015-06-16 9:50 ` [PATCH 5/5] Also look for debug files in gdb_sysroot Gary Benson
2015-07-01 13:45 ` Pedro Alves
2015-06-23 8:44 ` [PING][PATCH 0/5] Separate debugfile improvements Gary Benson
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=20150618105528.GA2644@blade.nx \
--to=gbenson@redhat.com \
--cc=cedric.buissart@gmail.com \
--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