Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA/commit/Windows] run program with space in path to exe.
Date: Sat, 20 Oct 2012 17:20:00 -0000	[thread overview]
Message-ID: <83a9vhdpth.fsf@gnu.org> (raw)
In-Reply-To: <20121020162936.GC3050@adacore.com>

> Date: Sat, 20 Oct 2012 09:29:36 -0700
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: gdb-patches@sourceware.org
> 
> > This is impossible, at least in the MinGW case: Windows file names
> > cannot include the quote character.  See
> > 
> >   http://msdn.microsoft.com/en-us/library/windows/desktop/aa365247%28v=vs.85%29.aspx
> 
> OK, great. I wasn't sure whether this was allowed or not. I was able
> to create a file with a double-quote, but that was under cygwin.

Cygwin employs some dark corners of NTFS to provide Posix-like
features.  A Cygwin GDB will indeed need to cope with quotes as part
of file names in this context.

> > But what happens if the program name is already quoted?  A user can do
> > that if she realizes the problem in advance, certainly if the program
> > name is specified at the GDB prompt, as in 'file "c:\foo bar\my.exe"'.
> > I think we should detect this case and not quote it again.
> 
> As per the above - this time, it's GDB that punts, so we never even
> get to the point where we can run the program.
> 
> > Also, what about the arguments to the program?  Don't they have the
> > same issue when you use --args on the GDB command line?
> 
> The arguments are always quoted properly by the generic portion of
> GDB.  No problem there.

Then I guess you can go ahead and commit the changes.  Thanks.


  reply	other threads:[~2012-10-20 17:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-20  0:29 Joel Brobecker
2012-10-20  8:03 ` Eli Zaretskii
2012-10-20 16:30   ` Joel Brobecker
2012-10-20 17:20     ` Eli Zaretskii [this message]
2012-10-24 13:42       ` Checked in: " Joel Brobecker
2012-10-24 14:34         ` Pedro Alves
2012-10-24 14:47           ` Joel Brobecker
2012-10-24 14:57             ` Pedro Alves
2012-10-24 15:01               ` Joel Brobecker
2012-10-24 15:08                 ` Pedro Alves
2012-10-25  2:48                 ` Christopher Faylor

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=83a9vhdpth.fsf@gnu.org \
    --to=eliz@gnu.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