From: Eli Zaretskii <eliz@gnu.org>
To: Don Breazeal <donb@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 3/4] Document RSP support for Linux exec events
Date: Sat, 24 May 2014 07:20:00 -0000 [thread overview]
Message-ID: <83d2f3lk23.fsf@gnu.org> (raw)
In-Reply-To: <1400885374-18915-4-git-send-email-donb@codesourcery.com>
> From: Don Breazeal <donb@codesourcery.com>
> Date: Fri, 23 May 2014 15:49:33 -0700
>
> This patch adds documentation of the new RSP support for exec events.
Thanks.
> +@cindex exec events, remote reply
> +@item exec
> +The packet indicates that @code{execve} was called, and @var{r} is the
> +absolute pathname of the file that was executed, in hex.
Please use "file name". GNU coding standards frown on using
"pathname" in this context.
> This is
> +only applicable to certain targets.
What is "only applicable to certain targets", the packet or the fact
that R is the file name of the exec'ed process?
I also think you should mention the fact that gdbserver supports
follow-exec-mode in the "Forks" node, as the text there does sound as
if this is only supported in native debugging.
next prev parent reply other threads:[~2014-05-24 7:20 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-30 19:18 [PATCH 0/0][REPOST] Exec events in gdbserver on Linux Don Breazeal
2014-04-30 19:18 ` [PATCH 4/4 v2][REPOST] Non-stop exec tests Don Breazeal
2014-04-30 19:18 ` [PATCH 3/4][REPOST] Document RSP support for Linux exec events Don Breazeal
2014-05-08 5:34 ` Yao Qi
2014-04-30 19:18 ` [PATCH 2/4][REPOST] Remote Linux ptrace " Don Breazeal
2014-05-07 20:01 ` Luis Machado
2014-05-09 21:17 ` Breazeal, Don
2014-05-08 5:44 ` Yao Qi
2014-05-21 15:28 ` Tom Tromey
2014-04-30 19:18 ` [PATCH 1/4][REPOST] Remote Linux ptrace exit events Don Breazeal
2014-05-07 19:40 ` Luis Machado
2014-05-08 5:23 ` Yao Qi
2014-05-09 21:03 ` Breazeal, Don
2014-05-21 15:15 ` Tom Tromey
2014-05-22 17:42 ` Breazeal, Don
2014-05-21 15:25 ` [PATCH 0/0][REPOST] Exec events in gdbserver on Linux Tom Tromey
2014-05-23 22:49 ` [PATCH 4/4] Non-stop exec tests Don Breazeal
2014-05-26 3:29 ` Doug Evans
2014-05-27 18:31 ` Breazeal, Don
2014-05-23 22:49 ` [PATCH 3/4] Document RSP support for Linux exec events Don Breazeal
2014-05-24 7:20 ` Eli Zaretskii [this message]
2014-05-27 21:28 ` Breazeal, Don
2014-05-28 14:22 ` Eli Zaretskii
2014-05-23 22:49 ` [PATCH 0/4 v3] Exec events in gdbserver on Linux Don Breazeal
2014-05-26 4:55 ` Doug Evans
2014-05-27 18:49 ` Breazeal, Don
2014-05-27 21:41 ` Breazeal, Don
2014-05-28 18:02 ` Breazeal, Don
2014-06-05 22:06 ` Breazeal, Don
2014-06-06 12:29 ` Luis Machado
2014-06-19 15:56 ` Breazeal, Don
2014-05-23 22:49 ` [PATCH 2/4 v3] Remote Linux ptrace exec events Don Breazeal
2014-05-23 22:49 ` [PATCH 1/4 v3] Remote Linux ptrace exit events Don Breazeal
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=83d2f3lk23.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=donb@codesourcery.com \
--cc=gdb-patches@sourceware.org \
/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