This is the mail archive of the mailing list for the GDB project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH v2 3/3] Target remote mode fork and exec docs

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.

Pedro Alves

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]