From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: gdb-patches@sourceware.org,
Pierre Muller <muller@ics.u-strasbg.fr>,
Eli Zaretskii <eliz@gnu.org>
Subject: Re: [RFC] win32-nat.c: Improve handling of 'set shell on'
Date: Thu, 10 Jan 2008 01:53:00 -0000 [thread overview]
Message-ID: <20080110015243.GA8464@ednor.casa.cgf.cx> (raw)
In-Reply-To: <utzlmsubo.fsf@gnu.org>
On Wed, Jan 09, 2008 at 08:54:51PM +0200, Eli Zaretskii wrote:
>> From: "Pierre Muller" <muller@ics.u-strasbg.fr>
>> Date: Wed, 9 Jan 2008 10:04:35 +0100
>>
>> I recently discovered that if you use
>> 'set shell on' on cygwin native, there are
>> some specific problems that appear.
>>
>> I ran the testsuite with a single line
>> modified:
>> -static int useshell = 0; /* use shell for subprocesses */
>> +static int useshell = 1; /* use shell for subprocesses */
>> Which made the use of shell to start the subprocess
>> the default.
>
>Is this really appropriate for the native Windows port of GDB as well
>as for Cygwin?
No. In fact, this really doesn't work all that well at all, AFAIK. The
current code represents my initial attempt to get it working but there
were problems which led me to believe that I needed to add some help in
Cygwin itself. I think that the main reason for wanting to use the
shell would be to interpret redirection and quoting characters and, last
I checked, that was not right. That's why it defaults to false.
cgf
next prev parent reply other threads:[~2008-01-10 1:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 9:05 Pierre Muller
2008-01-09 12:45 ` Daniel Jacobowitz
2008-01-09 18:56 ` Eli Zaretskii
2008-01-09 20:04 ` Joel Brobecker
2008-01-10 8:58 ` Pierre Muller
2008-01-10 1:53 ` Christopher Faylor [this message]
2008-01-10 4:27 ` Eli Zaretskii
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=20080110015243.GA8464@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@sourceware.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=muller@ics.u-strasbg.fr \
/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