aboutsummaryrefslogtreecommitdiff
path: root/gdb/doc
diff options
context:
space:
mode:
authorTom Tromey <tromey@adacore.com>2023-11-03 13:23:41 -0600
committerTom Tromey <tromey@adacore.com>2023-12-11 10:51:32 -0700
commite187e7c9696fbf66cf25d5fb8113bc3bc06b9e8b (patch)
treedb8bf8c6a14650905a6831cb35de0fea3e504510 /gdb/doc
parentf2e2493b1f892bd377b772307c5ad37bdcda4e12 (diff)
downloadgdb-e187e7c9696fbf66cf25d5fb8113bc3bc06b9e8b.zip
gdb-e187e7c9696fbf66cf25d5fb8113bc3bc06b9e8b.tar.gz
gdb-e187e7c9696fbf66cf25d5fb8113bc3bc06b9e8b.tar.bz2
Emit stop reason details in Python stop events
This changes Python stop events to carry a "details" dictionary, that holds any relevant information about the stop. The details are constructed using more or less the same procedure as is done for MI. Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=13587 Reviewed-By: Eli Zaretskii <eliz@gnu.org>
Diffstat (limited to 'gdb/doc')
-rw-r--r--gdb/doc/python.texi11
1 files changed, 11 insertions, 0 deletions
diff --git a/gdb/doc/python.texi b/gdb/doc/python.texi
index 3a35c5c..39137aa 100644
--- a/gdb/doc/python.texi
+++ b/gdb/doc/python.texi
@@ -3750,6 +3750,17 @@ registry extend @code{gdb.StopEvent}. As a child of
thread when @value{GDBN} is running in non-stop mode. Refer to
@code{gdb.ThreadEvent} above for more details.
+@code{gdb.StopEvent} has the following additional attributes:
+
+@defvar StopEvent.details
+A dictionary holding any details relevant to the stop. The exact keys
+and values depend on the type of stop, but are identical to the
+corresponding MI output (@pxref{GDB/MI Async Records}).
+
+A dictionary was used for this (rather than adding attributes directly
+to the event object) so that the MI keys could be used unchanged.
+@end defvar
+
Emits @code{gdb.SignalEvent}, which extends @code{gdb.StopEvent}.
This event indicates that the inferior or one of its threads has