From: Don Breazeal <donb@codesourcery.com>
To: <gdb-patches@sourceware.org>
Subject: [PATCH 3/4] Document RSP support for Linux exec events
Date: Fri, 23 May 2014 22:49:00 -0000 [thread overview]
Message-ID: <1400885374-18915-4-git-send-email-donb@codesourcery.com> (raw)
In-Reply-To: <1398885482-8449-1-git-send-email-donb@codesourcery.com>
This patch adds documentation of the new RSP support for exec events.
Regards,
--Don
gdb/
2014-05-22 Don Breazeal <donb@codesourcery.com>
* NEWS: Mention RSP Stop Reply Packet, new stop reason 'exec'.
Mention gdbserver support for exec events on Linux.
doc/
2014-05-22 Don Breazeal <donb@codesourcery.com>
* gdb.texinfo (Stop Reply Packets): Document RSP support
for exec events.
---
gdb/NEWS | 6 ++++++
gdb/doc/gdb.texinfo | 6 ++++++
2 files changed, 12 insertions(+), 0 deletions(-)
diff --git a/gdb/NEWS b/gdb/NEWS
index b23c8a0..ffe3520 100644
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -69,6 +69,8 @@ maint ada show ignore-descriptive-types
Timestamps can also be turned on with the
"monitor set debug-format timestamps" command from GDB.
+ ** GDBserver on GNU/Linux now supports exec events (follow-exec-mode).
+
* The 'record instruction-history' command now starts counting instructions
at one. This also affects the instruction ranges reported by the
'record function-call-history' command when given the /i modifier.
@@ -103,6 +105,10 @@ qXfer:btrace:read's annex
The qXfer:btrace:read packet supports a new annex 'delta' to read
branch trace incrementally.
+T Stop Reply Packet's reason
+ The T stop reply packet supports a new stop reason, 'exec', signifying
+ that the specified inferior executed a call to execve.
+
* Python Scripting
** Valid Python operations on gdb.Value objects representing
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 6092ff4..55f98c3 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -34589,6 +34589,12 @@ The packet indicates that the loaded libraries have changed.
@value{GDBN} should use @samp{qXfer:libraries:read} to fetch a new
list of loaded libraries. @var{r} is ignored.
+@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. This is
+only applicable to certain targets.
+
@cindex replay log events, remote reply
@item replaylog
The packet indicates that the target cannot continue replaying
--
1.7.0.4
next prev parent reply other threads:[~2014-05-23 22:49 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 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-04-30 19:18 ` [PATCH 2/4][REPOST] Remote Linux ptrace exec events 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 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-05-21 15:25 ` [PATCH 0/0][REPOST] Exec events in gdbserver on Linux Tom Tromey
2014-05-23 22:49 ` [PATCH 1/4 v3] Remote Linux ptrace exit events Don Breazeal
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 ` Don Breazeal [this message]
2014-05-24 7:20 ` [PATCH 3/4] Document RSP support for Linux " Eli Zaretskii
2014-05-27 21:28 ` Breazeal, Don
2014-05-28 14:22 ` Eli Zaretskii
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
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=1400885374-18915-4-git-send-email-donb@codesourcery.com \
--to=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