aboutsummaryrefslogtreecommitdiff
path: root/libctf
diff options
context:
space:
mode:
authorTom de Vries <tdevries@suse.de>2024-04-17 12:55:00 +0200
committerTom de Vries <tdevries@suse.de>2024-04-17 12:55:00 +0200
commitf0d556d14b1d1c3f8e2f9c13b08adca22e1b8c9c (patch)
treebd3b7d445200455d34afa4185bff05e26a12a47e /libctf
parent4f24b90aba691182e5093a6450e30fcb7d5dd803 (diff)
downloadgdb-f0d556d14b1d1c3f8e2f9c13b08adca22e1b8c9c.zip
gdb-f0d556d14b1d1c3f8e2f9c13b08adca22e1b8c9c.tar.gz
gdb-f0d556d14b1d1c3f8e2f9c13b08adca22e1b8c9c.tar.bz2
[gdb/testsuite] Fix end_sequence addresses
I noticed in test-case gdb.reverse/map-to-same-line.exp, that the end of main: ... 00000000004102c4 <end_of_sequence>: 4102c4: 52800000 mov w0, #0x0 // #0 4102c8: 9100c3ff add sp, sp, #0x30 4102cc: d65f03c0 ret ... is not described by the line table: ... File name Line number Starting address View Stmt ... map-to-same-line.c 54 0x4102ac x map-to-same-line.c - 0x4102c4 ... Fix this by ending the line table at $main_end. Likewise in a few other test-cases, found using: ... $ find gdb/testsuite/ -type f \ | xargs grep -B1 DW_LNE_end_sequence \ | grep set_address \ | egrep -v "_end|_len" ... Tested on aarch64-linux.
Diffstat (limited to 'libctf')
0 files changed, 0 insertions, 0 deletions