aboutsummaryrefslogtreecommitdiff
path: root/gdb/python/py-utils.c
diff options
context:
space:
mode:
authorAlexandra Hájková <ahajkova@redhat.com>2024-10-25 10:30:32 +0200
committerAlexandra Hájková <ahajkova@redhat.com>2024-11-08 22:15:50 +0100
commit21dc8b8d287f64a93e9762ba35d4400da124ea13 (patch)
tree3b872ac9f3cdc7543d57bc8e8477677f0628bc13 /gdb/python/py-utils.c
parent592e13ac900339405f1f7f639cb5fcad028958fb (diff)
downloadbinutils-21dc8b8d287f64a93e9762ba35d4400da124ea13.zip
binutils-21dc8b8d287f64a93e9762ba35d4400da124ea13.tar.gz
binutils-21dc8b8d287f64a93e9762ba35d4400da124ea13.tar.bz2
Add dw2-aranges.exp
This test checks that GDB is able to load DWARF information when .debug_aranges has a section address size that is set to 0. This test was originally written by Jan Kratochvil to test commit 927aa2e778d from 2017, titled "DWARF-5: .debug_names index consumer". This test was originally written using a static .S file and has been present in the Fedora tree for a long time. If dwarf2/aranges.c is modified to turn off the address_size check, GDB will crash with SIGFPE when loading the executable with address size set to zero. I modified the DWARF assembler to make it possible to set the address size to zero in a .debug_aranges section and used the DWARF assembler to produce the assembly file. Co-Authored-By: Jan Kratochvil <jan.kratochvil@redhat.com> Approved-by: Kevin Buettner <kevinb@redhat.com>
Diffstat (limited to 'gdb/python/py-utils.c')
0 files changed, 0 insertions, 0 deletions