From: Christopher Faylor <cgf@redhat.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: Fernando Nasser <fnasser@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFA] Re: DOS/Windows-specific code: cli-cmds.c
Date: Thu, 12 Jul 2001 10:21:00 -0000 [thread overview]
Message-ID: <20010712132145.B4589@redhat.com> (raw)
In-Reply-To: <200107120751.KAA17564@is.elta.co.il>
On Thu, Jul 12, 2001 at 10:51:59AM +0300, Eli Zaretskii wrote:
>> Date: Thu, 21 Jun 2001 12:47:14 -0400
>> From: David Taylor <taylor@candd.org>
>>
>> Date: Sun, 10 Jun 2001 16:28:57 +0300 (IDT)
>> From: Eli Zaretskii <eliz@is.elta.co.il>
>>
>> > Date: Tue, 8 May 2001 14:41:53 +0300 (IDT)
>> > From: Eli Zaretskii <eliz@is.elta.co.il>
>> >
>> > * cli-cmds.c:
>> >
>> > /* FIXME: this should be auto-configured! */
>> > #ifdef __MSDOS__
>> > # define CANT_FORK
>> > #endif
>> >
>> > This seems to cry for either an Autoconf test (based on whether the
>> > compiler defines __MSDOS__ or not) or perhaps the whole snippet should
>> > be moved to config/i386/xm-go32.h.
>> >
>> >
>> > * cli-cmds.c:shell_escape()
>> >
>> > #ifdef __DJGPP__
>> > /* Make sure to return to the directory GDB thinks it is, in case the
>> > shell command we just ran changed it. */
>> > chdir (current_directory);
>> > #endif
>> >
>> > This code is there because the current working directory is a global
>> > notion (as opposed to being private to each process on Posix
>> > systems). Windows ports, at least the non-Cygwin ones, probably want
>> > this as well. Suggestions how to test this, anyone? Should we define
>> > a GLOBAL_CURDIR macro (zero by default)?
>>
>> Here's the patch to fix these two issues. Okay to commit?
>>
>>
>> 2001-06-10 Eli Zaretskii <eliz@is.elta.co.il>
>>
>> * cli/cli-cmds.c (shell_escape) [GLOBAL_CURDIR]: Condition the
>> call to chdir on this symbol rather than on __DJGPP__.
>> (CANT_FORK) [__MSDOS__]: Move from here...
>> * defs.h (CANT_FORK) [__MSDOS__]: ...to here.
>> (GLOBAL_CURDIR) [__MSDOS__]: Define.
>>
>> Sorry for the delay. The defs.h part is approved.
>
>Fernando, could you please review this? Thanks.
FWIW, Cygwin doesn't need any special chdir considerations. This
should be a MSDOS only issue.
cgf
next prev parent reply other threads:[~2001-07-12 10:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-21 9:47 David Taylor
2001-06-21 11:44 ` Eli Zaretskii
2001-07-12 0:50 ` Eli Zaretskii
2001-07-12 5:29 ` Fernando Nasser
2001-07-12 8:07 ` Eli Zaretskii
2001-07-12 10:21 ` Christopher Faylor [this message]
2001-07-12 11:22 ` Eli Zaretskii
2001-07-12 11:27 ` Christopher Faylor
2001-07-12 15:38 ` Fernando Nasser
2001-07-16 7:14 ` Eli Zaretskii
[not found] <20010503211502.21716.qmail@web6401.mail.yahoo.com>
[not found] ` <3AF1DAA0.3060702@cygnus.com>
[not found] ` <200105071609.TAA24129@is.elta.co.il>
[not found] ` <200105081141.OAA06131@is.elta.co.il>
2001-06-10 6: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=20010712132145.B4589@redhat.com \
--to=cgf@redhat.com \
--cc=eliz@is.elta.co.il \
--cc=fnasser@redhat.com \
--cc=gdb-patches@sources.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