diff mbox

[3/4] Document RSP support for Linux exec events

Message ID 1400885374-18915-4-git-send-email-donb@codesourcery.com
State New, archived
Headers

Commit Message

Don Breazeal May 23, 2014, 10:49 p.m. UTC 
  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(-)

Comments

Eli Zaretskii May 24, 2014, 7:20 a.m. UTC | #1 
> 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.
diff mbox

Patch

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