Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: gdb-patches@sourceware.org, Joel Brobecker <brobecker@adacore.com>
Subject: Re: [RFC] Do not treat '\' as escape character on MinGW Windows  hosts
Date: Wed, 21 Apr 2010 22:08:00 -0000	[thread overview]
Message-ID: <20100421220828.GA19620@ednor.casa.cgf.cx> (raw)
In-Reply-To: <20100421203354.GD6588@adacore.com>

On Wed, Apr 21, 2010 at 04:33:54PM -0400, Joel Brobecker wrote:
>Hello,
>
>With the MinGW debugger, it is currently not possible to use a path
>that follows the Windows convention.  For instance:
>
>        (gdb) file c:\foo\bar.exe
>        c:foobar.exe: No such file or directory.
>
>This is because the routine that parses arguments treats all backslashes
>as an escape character.  With a MinGW tool, this does not make sense
>when the argument is a path, since the canonical directory separator
>on Windows is a backslash...
>
>What the user has to do, at this point, is escape every backslash,
>which can be quite painful when the path starts getting longer...
>
>        (gdb) file c:\\foo\\bar.exe
>        Reading symbols from c:\foo\bar.exe...done.

Why not just use a "forward" slash?

cgf


  reply	other threads:[~2010-04-21 22:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-21 20:34 Joel Brobecker
2010-04-21 22:08 ` Christopher Faylor [this message]
2010-04-22  0:17   ` Joel Brobecker
2010-04-22  2:34     ` Christopher Faylor
2010-04-22  8:17       ` Mark Kettenis
2010-04-22 10:37       ` Joel Brobecker
2010-04-22 11:51         ` Joel Brobecker
2010-04-22 12:01           ` Pierre Muller
2010-04-22 12:26             ` Joel Brobecker
2010-04-22 11:54         ` Chris Moller
2010-04-22 12:33           ` Joel Brobecker
2010-04-22 11:49       ` Chris Moller
2010-04-22 12:47       ` André Pönitz
2010-05-05 18:49 ` Joel Brobecker
2010-05-06 23:56   ` Sergio Durigan Junior
2010-06-04 21:53     ` Tom Tromey

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=20100421220828.GA19620@ednor.casa.cgf.cx \
    --to=cgf-use-the-mailinglist-please@sourceware.org \
    --cc=brobecker@adacore.com \
    --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