aboutsummaryrefslogtreecommitdiff
path: root/gdb/testsuite/gdb.python
diff options
context:
space:
mode:
authorTom de Vries <tdevries@suse.de>2022-07-22 23:50:48 +0200
committerTom de Vries <tdevries@suse.de>2022-07-22 23:50:48 +0200
commit263ad5cc818ef8f7700c82f2aecd2a929dbd3be5 (patch)
tree6334604f9cada900b5945c91d6d60dd24ebed15f /gdb/testsuite/gdb.python
parent5ae3df226b1b1e45b9326a5eee81b92489ae52f2 (diff)
downloadbinutils-263ad5cc818ef8f7700c82f2aecd2a929dbd3be5.zip
binutils-263ad5cc818ef8f7700c82f2aecd2a929dbd3be5.tar.gz
binutils-263ad5cc818ef8f7700c82f2aecd2a929dbd3be5.tar.bz2
[gdb/symtab] Fix duplicate CUs in all_comp_units
When running test-case gdb.cp/cpexprs-debug-types.exp with target board cc-with-debug-names on a system with gcc 12.1.1 (defaulting to dwarf 5), I run into: ... (gdb) file cpexprs-debug-types^M Reading symbols from cpexprs-debug-types...^M warning: Section .debug_aranges in cpexprs-debug-types has duplicate \ debug_info_offset 0x0, ignoring .debug_aranges.^M gdb/dwarf2/read.h:309: internal-error: set_length: \ Assertion `m_length == length' failed.^M ... The exec contains a .debug_names section, which gdb rejects due to .debug_names containing a list of TUs, while the exec doesn't contain a .debug_types section (which is what you'd expect for dwarf 4). Gdb then falls back onto the cooked index, which calls create_all_comp_units to create all_comp_units. However, the failed index reading left some elements in all_comp_units, so we end up with duplicates in all_comp_units, which causes the misleading complaint and the assert. Fix this by: - asserting at the start of create_all_comp_units that all_comp_units is empty, as we do in create_cus_from_index and create_cus_from_debug_names, and - cleaning up all_comp_units when failing in dwarf2_read_debug_names. Add a similar cleanup in dwarf2_read_gdb_index. Tested on x86_64-linux. Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=29381
Diffstat (limited to 'gdb/testsuite/gdb.python')
0 files changed, 0 insertions, 0 deletions