This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: Initialize the correct cwd for the child
- To: robert dot hoehne at gmx dot net
- Subject: Re: Initialize the correct cwd for the child
- From: Eli Zaretskii <eliz at delorie dot com>
- Date: Fri, 4 Aug 2000 14:11:26 -0400 (EDT)
- CC: gdb-patches at sourceware dot cygnus dot com
- References: <200008041341.PAA15581@robby.dittmannsdorf.de>
- Reply-to: Eli Zaretskii <eliz at is dot elta dot co dot il>
> From: Robert Hoehne <robert.hoehne@gmx.net>
> Date: Fri, 4 Aug 2000 15:43:26 +0200
>
> On DJGPP, the child's working directory have to be remembered.
> In the current implementation this is done once, when gdb is started.
> But this is wrong, since the user can change it with the gdb-command
>
> cd <some-directory>
>
> and when running the child, it is expected, that it get this directory as
> its starting directory. So I made a patch for this.
Thanks for the patch. However, I wonder: what would be the cwd of an
inferior on Unix, after the following commands:
gdb foo
cd bar
run
I think the DJGPP port should, as much as possible, behave the same
way as GDB does on Unix.