Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: Pedro Alves <palves@redhat.com>,
	gdb-patches@sourceware.org,
	Joel Brobecker <brobecker@adacore.com>
Subject: Re: Checked in: [RFA/commit/Windows] run program with space in path to exe.
Date: Thu, 25 Oct 2012 02:48:00 -0000	[thread overview]
Message-ID: <20121025024839.GA13308@ednor.casa.cgf.cx> (raw)
In-Reply-To: <20121024150151.GJ3555@adacore.com>

On Wed, Oct 24, 2012 at 11:01:51AM -0400, Joel Brobecker wrote:
>> Ah.  The "image name" is a mandatory argument on Windows CE, not optional.
>> Are you saying that that would be an alternative fix for gdb?  Or is there a
>> downside?  (Wondering in the sake of convergence in the code bases.)
>
>We can provide the image name, but we still need to quote it in
>the command line, because otherwise, argv is improperly computed.
>For instance, instead of being:
>
>  ["/path/to/space dir/exe", "arg1"]
>
>The program would see:
>
>  ["/path/to/space", "dir/exe", "arg1"]
>
>/me wishes that CreateProcess was taking a list of arguments, rather
>than a string of space-separated tokens....

Yeah, tell me about it.  We actually pass a real argv list in Cygwin.
The "one long command line" method is rather dumb.  Much of the Windows
API is not that bad but this is, IMO, one glaring flaw.

cgf


      parent reply	other threads:[~2012-10-25  2:48 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
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 [this message]

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=20121025024839.GA13308@ednor.casa.cgf.cx \
    --to=cgf-use-the-mailinglist-please@sourceware.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@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