diff options
| author | Guinevere Larsen <blarsen@redhat.com> | 2023-11-01 17:25:32 +0100 |
|---|---|---|
| committer | Guinevere Larsen <blarsen@redhat.com> | 2024-01-02 10:21:37 +0100 |
| commit | 528b729be1a293a21f44149351f3eba5b4e2d870 (patch) | |
| tree | 3959ec9a424c769dfeffe89440fc4c6165df3916 /gdb/NEWS | |
| parent | b22ee0e49ba2bac8a5295f0426c62e9bd2b311a1 (diff) | |
| download | gdb-528b729be1a293a21f44149351f3eba5b4e2d870.zip gdb-528b729be1a293a21f44149351f3eba5b4e2d870.tar.gz gdb-528b729be1a293a21f44149351f3eba5b4e2d870.tar.bz2 | |
gdb/dwarf2: Add support for DW_LNS_set_epilogue_begin in line-table
This commit adds a mechanism for GDB to detect the linetable opcode
DW_LNS_set_epilogue_begin. This opcode is set by compilers to indicate
that a certain instruction marks the point where the frame is destroyed.
While the standard allows for multiple points marked with epilogue_begin
in the same function, for performance reasons, the function that
searches for the epilogue address will only find the last address that
sets this flag for a given block.
This commit also changes amd64_stack_frame_destroyed_p_1 to attempt to
use the epilogue begin directly, and only if an epilogue can't be found
will it attempt heuristics based on the current instruction.
Finally, this commit also changes the dwarf assembler to be able to emit
epilogue-begin instructions, to make it easier to test this patch
Approved-By: Tom Tromey <tom@tromey.com>
Diffstat (limited to 'gdb/NEWS')
| -rw-r--r-- | gdb/NEWS | 5 |
1 files changed, 5 insertions, 0 deletions
@@ -16,6 +16,11 @@ disassemble command will now give an error. Previously the 'b' flag would always override the 'r' flag. +maintenance info line-table + Add an EPILOGUE-BEGIN column to the output of the command. It indicates + if the line is considered the start of the epilgoue, and thus a point at + which the frame can be considered destroyed. + * New commands info missing-debug-handler |