diff options
author | Bruno Larsen <blarsen@redhat.com> | 2022-11-03 10:17:36 +0100 |
---|---|---|
committer | Bruno Larsen <blarsen@redhat.com> | 2023-01-04 11:21:57 +0100 |
commit | e24d337e219da287535eddc5c9918ac410d124be (patch) | |
tree | b13e90469ebd1690ffeb755eb1ccaab6471d2a60 /gas/bit_fix.h | |
parent | 502c7218da3c486e58d6ce039b36fb4fa62d3a92 (diff) | |
download | gdb-e24d337e219da287535eddc5c9918ac410d124be.zip gdb-e24d337e219da287535eddc5c9918ac410d124be.tar.gz gdb-e24d337e219da287535eddc5c9918ac410d124be.tar.bz2 |
gdb: add 'maintenance print record-instruction' command
While chasing some reverse debugging bugs, I found myself wondering what
was recorded by GDB to undo and redo a certain instruction. This commit
implements a simple way of printing that information.
If there isn't enough history to print the desired instruction (such as
when the user hasn't started recording yet or when they request 2
instructions back but only 1 was recorded), GDB warns the user like so:
(gdb) maint print record-instruction
Not enough recorded history
If there is enough, GDB prints the instruction like so:
(gdb) maint print record-instruction
4 bytes of memory at address 0x00007fffffffd5dc changed from: 01 00 00 00
Register eflags changed: [ IF ]
Register rip changed: (void (*)()) 0x401115 <main+15>
Approved-by: Eli Zaretskii <eliz@gnu.org>
Reviewed-by: Alexandra Hajkova <ahajkova@redhat.com>
Reviewed-by: Lancelot Six <lsix@lancelotsix.com>
Approved-by: Tom Tromey <tom@tromey.com>
Diffstat (limited to 'gas/bit_fix.h')
0 files changed, 0 insertions, 0 deletions