From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Jon Beniston <jon@beniston.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Don't split executable paths with spaces in into multiple arguments
Date: Mon, 09 Nov 2009 17:42:00 -0000 [thread overview]
Message-ID: <m31vk7k33w.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20091104161727.GH4557@adacore.com> (Joel Brobecker's message of "Wed, 4 Nov 2009 08:17:27 -0800")
>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:
>> gdb/
>> 2009-11-04 Jon Beniston <jon@beniston.com>
>> * remote-sim.c(gdbsim_create_inferior) Quote executable path in case
>> it
>> contains spaces.
Joel> OK. This is not handling the case where the filename contains a double
Joel> quote, but it is not making things worse, and double-quotes in filenames
Joel> are probably extremely rare.
It seems to me that it would not be significantly harder for the code to
do the correct thing in all cases.
Tom
next prev parent reply other threads:[~2009-11-09 17:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-04 13:26 Jon Beniston
2009-11-04 16:17 ` Joel Brobecker
2009-11-09 17:42 ` Tom Tromey [this message]
2009-11-09 17:46 ` Joel Brobecker
2009-11-09 18:04 ` Tom Tromey
2009-11-09 21:11 ` Joel Brobecker
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=m31vk7k33w.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jon@beniston.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