diff options
| author | Felix Willgerodt <felix.willgerodt@intel.com> | 2023-06-28 10:15:04 +0200 |
|---|---|---|
| committer | Felix Willgerodt <felix.willgerodt@intel.com> | 2024-09-24 14:22:28 +0200 |
| commit | 13b3a89bc272ded10242e3359bc0871e99338e6c (patch) | |
| tree | 52e34dd924f471a23727c1039df906ae9e413f24 /gdb/NEWS | |
| parent | 48bc2f1c65751a87d6212e1241b45fc8640f0f83 (diff) | |
| download | fsf-binutils-gdb-13b3a89bc272ded10242e3359bc0871e99338e6c.zip fsf-binutils-gdb-13b3a89bc272ded10242e3359bc0871e99338e6c.tar.gz fsf-binutils-gdb-13b3a89bc272ded10242e3359bc0871e99338e6c.tar.bz2 | |
btrace: Enable event tracing on Linux for Intel PT.
Event tracing allows GDB to show information about interesting asynchronous
events when tracing with Intel PT. Subsequent patches will add support for
displaying each type of event.
Enabling event-tracing unconditionally would result in rather noisy output, as
breakpoints themselves result in interrupt events. Which is why this patch adds
a set/show command to allow the user to enable/disable event-tracing before
starting a recording. The event-tracing setting has no effect on an already
active recording. The default setting is off. As event tracing will use the
auxiliary infrastructure added by ptwrite, the user can still disable printing
events, even when event-tracing was enabled, by using the /a switch for the
record instruction-history/function-call-history commands.
Reviewed-By: Eli Zaretskii <eliz@gnu.org>
Approved-By: Markus Metzger <markus.t.metzger@intel.com>
Diffstat (limited to 'gdb/NEWS')
| -rw-r--r-- | gdb/NEWS | 5 |
1 files changed, 5 insertions, 0 deletions
@@ -3,6 +3,11 @@ *** Changes since GDB 15 +* GDB now supports printing of asynchronous events from the Intel Processor + Trace during 'record instruction-history', 'record function-call-history' + and all stepping commands. This can be controlled with the new + "set record btrace pt event-tracing" command. + * GDB now supports printing of ptwrite payloads from the Intel Processor Trace during 'record instruction-history', 'record function-call-history' and all stepping commands. The payload is also accessible in Python as a |