From mboxrd@z Thu Jan  1 00:00:00 1970
From: Tom Tromey <tromey@redhat.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFC: Inferior command line arguments
Date: Fri, 28 Sep 2001 07:50:00 -0000
Message-id: <8766a3gy0m.fsf@creche.redhat.com>
References: <87zo7gq7gb.fsf@creche.redhat.com> <2593-Fri28Sep2001103201+0300-eliz@is.elta.co.il> <87u1xnh4ns.fsf@creche.redhat.com> <4331-Fri28Sep2001162207+0300-eliz@is.elta.co.il>
X-SW-Source: 2001-09/msg00416.html

>>>>> "Eli" == Eli Zaretskii <eliz@is.elta.co.il> writes:

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.

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?

Tom