Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: gdb-patches@sourceware.org, palves@redhat.com
Subject: Re: [PATCH/RFC] Implement the ability to set the current working directory in GDBserver
Date: Wed, 30 Aug 2017 14:29:00 -0000	[thread overview]
Message-ID: <83bmmx2kpq.fsf@gnu.org> (raw)
In-Reply-To: <20170830043811.776-1-sergiodj@redhat.com> (message from Sergio	Durigan Junior on Wed, 30 Aug 2017 00:38:11 -0400)

> From: Sergio Durigan Junior <sergiodj@redhat.com>
> Cc: Pedro Alves <palves@redhat.com>,
> 	Eli Zaretskii <eliz@gnu.org>,
> 	Sergio Durigan Junior <sergiodj@redhat.com>
> Date: Wed, 30 Aug 2017 00:38:11 -0400
> 
> --- a/gdb/NEWS
> +++ b/gdb/NEWS
> @@ -17,11 +17,22 @@
>       "target remote", you can disable the startup with shell by using the
>       new "--no-startup-with-shell" GDBserver command line option.
>  
> +  ** On Unix systems, GDBserver is now able to enter a directory
> +     before starting an inferior.

Can you tell why this is limited to Unix systems?  The chdir function
is available much wider than just on Unix.

> +     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?

> +Whenever you specify a new working directory in @value{GDBN}, and if
> +you are performing a remote debug (@pxref{Remote Debugging}), this
> +change will be reflected in @command{gdbserver} the next time you run
> +the program being debugged (@pxref{QSetWorkingDir packet}).  Sometimes
> +you may want to make @command{gdbserver} enter a directory in which
> +@value{GDBN} is already in; in this case, you can perform a @code{cd
> +.} which will not change the current directory in @value{GDBN} but
> +will force @command{gdbserver} to enter it.

The "@code{cd .}" part should be @kbd{cd .}, and I'd take it in @w{..}
for a good measure, to prevent it from being broken between 2 lines.

> +This packet is only transmitted when the user issues a @code{cd}
> +command in @value{GDBN} (@xref{Working Directory, ,Your Program's
> +Working Directory}).

The @xref should be @pxref, as the former is not appropriate in
parentheses.

The documentation parts are okay with these nits fixed.

Thanks.


  reply	other threads:[~2017-08-30 14:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-30  4:38 Sergio Durigan Junior
2017-08-30 14:29 ` Eli Zaretskii [this message]
2017-08-31 21:41   ` Sergio Durigan Junior
2017-09-01 12:32     ` Philippe Waroquiers
2017-09-01 18:40       ` Sergio Durigan Junior
2017-08-31 22:01 ` Pedro Alves
2017-08-31 22:42   ` John Baldwin
2017-09-05 17:45   ` Sergio Durigan Junior
2017-09-06 14:20     ` Pedro Alves
2017-09-06 18:18       ` Sergio Durigan Junior

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=83bmmx2kpq.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --cc=sergiodj@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