diff options
| author | Andrew Burgess <aburgess@redhat.com> | 2022-08-16 16:48:01 +0100 |
|---|---|---|
| committer | Andrew Burgess <aburgess@redhat.com> | 2022-08-24 14:44:20 +0100 |
| commit | 70175292616118bad315296ba6180f375326bb6c (patch) | |
| tree | d8d27502ccae432ab24e068dc659f864546e7089 /configure | |
| parent | 42bd5254fb5f52f045796e1d9cce07102881d3b1 (diff) | |
| download | gdb-70175292616118bad315296ba6180f375326bb6c.zip gdb-70175292616118bad315296ba6180f375326bb6c.tar.gz gdb-70175292616118bad315296ba6180f375326bb6c.tar.bz2 | |
gdb: new 'maint print frame-id' command
When debugging a certain class of GDB bug, I often end up wanting to
know what GDB thinks the frame-id is in a particular frame. It's
not too hard to pull this from some debug output, but I thought it
might be nice if there was a maintenance command that could tell us.
This commit adds 'maint print frame-id' which prints the frame-id of
the currently selected frame. You can also pass a frame level number
to find the frame-id for a specific frame.
There's a new test too.
Diffstat (limited to 'configure')
0 files changed, 0 insertions, 0 deletions