Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: tromey@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFC: Inferior command line arguments
Date: Fri, 28 Sep 2001 09:25:00 -0000	[thread overview]
Message-ID: <1858-Fri28Sep2001182535+0300-eliz@is.elta.co.il> (raw)
In-Reply-To: <8766a3gy0m.fsf@creche.redhat.com>

> From: Tom Tromey <tromey@redhat.com>
> Date: 28 Sep 2001 09:01:29 -0600
> 
> Eli> Oh, so in the comment above that confused me you meant ``...will
> Eli> be parsed _by_the_shell_ to yield the same vector'', yes?
> 
> Yeah.  I changed it to read:
> 
>     /* Given a vector of command-line arguments, return a newly allocated
>        string which, when passed to the create_inferior function, will be
>        parsed (on Unix systems, by the shell) to yield the same vector.

Thanks.

> Eli> AFAIK, CreateProcess acts like a stock Windows shell wrt the
> Eli> command line handling.
> 
> I ended up implementing this for win32-nat.c:
> 
>   /* We quote each argument by adding "..." around it.  If the
>      argument contains a quote character, we quote that with a
>      backslash.  */
> 
> I did this based on some readings I found via a google search.  I
> really know very little about Windows.  Does this approach sound
> reasonable?

That is correct AFAIK, but there are complications: the case where the
embedded quote is already preceded by a backslash, and the case where
the argument that needs to be wrapped in quotes ends in a backslash.
And running Cygwin applications needs yet another modification.  For
the full story, see the function sys_spawnve on w32proc.c in the Emacs
distribution.


  reply	other threads:[~2001-09-28  9:25 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-27 21:02 Tom Tromey
2001-09-28  1:31 ` Eli Zaretskii
2001-09-28  5:26   ` Tom Tromey
2001-09-28  7:21     ` Eli Zaretskii
2001-09-28  7:50       ` Tom Tromey
2001-09-28  9:25         ` Eli Zaretskii [this message]
2001-09-30 12:07           ` Christopher Faylor
2001-10-01  0:39             ` Eli Zaretskii
2001-10-01  8:07               ` Tom Tromey
2001-10-01  8:10                 ` Christopher Faylor
2001-09-28 11:24 ` Michael Snyder
2001-09-28 11:32   ` Tom Tromey
2001-09-28 11:59     ` Daniel Jacobowitz
2001-09-28 12:24       ` Tom Tromey
2001-09-29  2:23         ` Eli Zaretskii
2001-09-28 12:27       ` Andrew Cagney
2001-09-28 12:42         ` Daniel Jacobowitz
2001-09-28 14:19           ` Tom Tromey
2001-09-28 14:22             ` Daniel Jacobowitz
2001-09-29  1:23             ` David Deephanphongs
2001-10-01  8:09               ` 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=1858-Fri28Sep2001182535+0300-eliz@is.elta.co.il \
    --to=eliz@is.elta.co.il \
    --cc=gdb-patches@sources.redhat.com \
    --cc=tromey@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