From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Eli Zaretskii'" <eliz@gnu.org>, "'Tom Tromey'" <tromey@redhat.com>
Cc: <gdb-patches@sourceware.org>
Subject: RE: [RFC] Fix problems related to Mingw/DJGPP file names containing colons
Date: Sat, 13 Aug 2011 10:11:00 -0000 [thread overview]
Message-ID: <003c01cc59a1$49cc1520$dd643f60$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <83sjp6wmhb.fsf@gnu.org>
> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Eli Zaretskii
> Envoyé : vendredi 12 août 2011 19:47
> À : Tom Tromey
> Cc : pierre.muller@ics-cnrs.unistra.fr; gdb-patches@sourceware.org
> Objet : Re: [RFC] Fix problems related to Mingw/DJGPP file names
containing
> colons
>
> > From: Tom Tromey <tromey@redhat.com>
> > Cc: Pierre Muller <pierre.muller@ics-cnrs.unistra.fr>,
> > gdb-patches@sourceware.org
> > Date: Fri, 12 Aug 2011 11:24:56 -0600
> >
> > Eli> Thanks for working on this, but I don't like the idea of quoting
file
> > Eli> names internally just to work around this problem.
> >
> > Why?
>
> It's ugly and fragile, because the original name could be quoted.
+ /* Quote filenames containing ':' characters to avoid problems. */
+ if (strchr (filename, ':') != NULL && filename[0] != '"')
+ sprintf (canonical_name, "\"%s\":%d", filename, sal->line);
The second condition already takes care of not
quoting already quoted file names.
Regarding the reverting of
As Keith said, I can solve this problem only by revert this change:
------------------------------
if (!*p
|| p[0] == '\t'
- || ((p[0] == ':')
- && ((p[1] == ':') || (strchr (p + 1, ':') == NULL)))
+ || (p[0] == ':')
This probably creates problems with some C++
cases that use '::' patterns, no?
Pierre
next prev parent reply other threads:[~2011-08-13 10:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <004901cc5907$85006320$8f012960$%muller@ics-cnrs.unistra.fr>
2011-08-12 17:17 ` Eli Zaretskii
2011-08-12 17:25 ` Tom Tromey
2011-08-12 17:47 ` Eli Zaretskii
2011-08-13 10:11 ` Pierre Muller [this message]
[not found] ` <003c01cc59a1$49cc1520$dd643f60$%muller@ics-cnrs.unistra.fr>
2011-08-13 10:50 ` Eli Zaretskii
2011-08-13 20:42 ` Pierre Muller
2011-08-13 20:51 ` DJ Delorie
2011-08-13 21:26 ` Mark Kettenis
2011-08-15 19:29 ` Tom Tromey
[not found] ` <28604.9419818029$1313268187@news.gmane.org>
2011-08-15 19:21 ` Tom Tromey
[not found] <7973.24406817115$1313164244@news.gmane.org>
2011-08-13 1:20 ` asmwarrior
2011-08-12 15:50 Pierre Muller
2011-08-12 17:00 ` Keith Seitz
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='003c01cc59a1$49cc1520$dd643f60$@muller@ics-cnrs.unistra.fr' \
--to=pierre.muller@ics-cnrs.unistra.fr \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.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