From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andrew Cagney <ac131313@cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>, gdb@sources.redhat.com
Subject: Re: DOS/Windows-specific code: cli-cmds.c
Date: Tue, 08 May 2001 17:56:00 -0000
Message-id: <3AF895D0.4030007@cygnus.com>
References: <20010503211502.21716.qmail@web6401.mail.yahoo.com> <3AF1DAA0.3060702@cygnus.com> <200105071609.TAA24129@is.elta.co.il> <200105081141.OAA06131@is.elta.co.il>
X-SW-Source: 2001-05/msg00160.html

>  * 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)?


GDB, may its self, one day need some similar notion of current directory.

Consider a debug environment containing:

	o	core/lib-gdb
	o	a GUI/MI
	o	a CLI

Should the user entering CLI commands that change the GDB processes 
apparent directory affect the GUI?

	Andrew