This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [RFA/commit/Windows] run program with space in path to exe.


> 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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]