This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH/RFC] Implement the ability to set the current working directory in GDBserver
- From: Philippe Waroquiers <philippe dot waroquiers at skynet dot be>
- To: Sergio Durigan Junior <sergiodj at redhat dot com>
- Cc: Eli Zaretskii <eliz at gnu dot org>, gdb-patches at sourceware dot org, palves at redhat dot com
- Date: Fri, 01 Sep 2017 14:33:35 +0200
- Subject: Re: [PATCH/RFC] Implement the ability to set the current working directory in GDBserver
- Authentication-results: sourceware.org; auth=none
- References: <20170830043811.776-1-sergiodj@redhat.com> <83bmmx2kpq.fsf@gnu.org> <8737875sbb.fsf@redhat.com>
On Thu, 2017-08-31 at 17:40 -0400, Sergio Durigan Junior wrote:
> >> + This is done by using the "cd" command in GDB, which instructs it
> >> + to tell GDBserver about this directory change the next time an
> >> + inferior is run. If you want to make GDBserver enter the
> >> + directory your GDB is currently in, you can do a "cd ." in GDB.
> >
> > Couldn't GDB do this "cd ." step under the hood, without bothering
> > users with that?
>
> The problem is that we don't really know if the user will want to change
> gdbserver's current directory or not. If we always assume so, this will
> lead to many breakages as the directory tree will not be always the same
> on host and target. That's why 'user_set_cwd' is initially false.
> However, there's the case when the user may want to change gdbserver's
> directory to the same directory GDB is in. That's why I included this
> explanation in the docs.
>
> The more I think about this, the less I'm satisfied with the current
> solution. But I can't really think of a better alternative that doesn't
> involve having a separate command to manipulate gdbserver's cwd.
Why not have options such as:
cd -s xxxx
only change the gdb server directory
cd -g xxxx
only change the gdb directory
cd xxxx
change both gdb and gdb server directory
(synonym of cd -s -g xxxx)
Philippe