This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH v2 3/3] Target remote mode fork and exec docs
- From: Pedro Alves <palves at redhat dot com>
- To: Don Breazeal <donb at codesourcery dot com>, gdb-patches at sourceware dot org
- Date: Tue, 08 Dec 2015 13:07:07 +0000
- Subject: Re: [PATCH v2 3/3] Target remote mode fork and exec docs
- Authentication-results: sourceware.org; auth=none
- References: <564F1A6A dot 3030301 at redhat dot com> <1449526447-10039-1-git-send-email-donb at codesourcery dot com> <1449526447-10039-4-git-send-email-donb at codesourcery dot com>
On 12/07/2015 10:14 PM, Don Breazeal wrote:
> diff --git a/gdb/NEWS b/gdb/NEWS
> index a222dfb..bec9810 100644
> --- a/gdb/NEWS
> +++ b/gdb/NEWS
> @@ -127,6 +127,15 @@ show remote exec-event-feature-packet
> The reply to qXfer:threads:read may now include a name attribute for each
> thread.
>
> +* Target remote mode fork and exec events
> +
> + ** GDB now has support for fork and exec events on target remote mode
> + Linux targets. For such targets with Linux kernels 2.5.46 and later,
> + this enables follow-fork-mode, detach-on-fork, follow-exec-mode, and
> + fork and exec catchpoints. Note that follow-exec-mode is of limited
> + usefulness, because target remote mode does not support the 'run'
> + command.
...
>
> +@code{follow-exec-mode} is supported in native mode and
> +@code{target extended-remote} mode. It is of limited usefulness in
> +@code{target remote} mode since the run command is not supported in that
> +mode.
Thinking about this some more, I'm really not sure we should be calling out
this limited usefulness here (and NEWS). It seems just as useful in
remote mode -- it's just that when you want to restart the debugging from
the starting binary, you do "target remote" again instead of "run" then.
Thanks,
Pedro Alves