[Bug symtab/29453] New: [gdb/symtab] read.h:309: internal-error: set_length: Assertion `m_length == length' failed

vries at gcc dot gnu.org sourceware-bugzilla@sourceware.org
Sun Aug 7 06:59:06 GMT 2022


https://sourceware.org/bugzilla/show_bug.cgi?id=29453

            Bug ID: 29453
           Summary: [gdb/symtab] read.h:309: internal-error: set_length:
                    Assertion `m_length == length' failed
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: symtab
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

With this change:
...
diff --git a/gdb/testsuite/gdb.dwarf2/debug-names.exp
b/gdb/testsuite/gdb.dwarf2/debug-names.exp
index 0af5a93bea8..f82e53d5cba 100644
--- a/gdb/testsuite/gdb.dwarf2/debug-names.exp
+++ b/gdb/testsuite/gdb.dwarf2/debug-names.exp
@@ -29,7 +29,7 @@ set func_info_vars \
 set asm_file [standard_output_file $srcfile2]
 Dwarf::assemble {
     filename $asm_file
-    add_dummy_cus 0
+    add_dummy_cus 1
 } {
     global func_info_vars
     foreach var $func_info_vars {
...
we run into:
...
(gdb) break _start^M
/home/vries/gdb_versions/devel/src/gdb/dwarf2/read.h:309: internal-error:
set_length: Assertion `m_length == length' failed.^M
A problem internal to GDB has been detected,^M
further debugging may prove unreliable.^M
----- Backtrace -----^M
FAIL: gdb.dwarf2/debug-names.exp: gdb_breakpoint: set breakpoint at _start (GDB
internal error)
...

There are 3 CUs:
...
$ readelf -wi outputs/gdb.dwarf2/debug-names/debug-names | grep @
  Compilation Unit @ offset 0x0:
  Compilation Unit @ offset 0xb:
  Compilation Unit @ offset 0x38:
...
but the CU list in .debug_names only contains one:
...
Contents of the .debug_names section:

Version 5
Augmentation string: 47 44 42 00  ("GDB")
CU table:
[  0] 0xb

TU table:
...

The length of the CU at 0xb is calculated in create_cus_from_debug_names_list
as if the CU at 0x38 is also a part of it.

Then when doing full expansion, the actual CU header is read, and we find out
the size is different:
...
#6  0x0000000000718b2f in dwarf2_per_cu_data::set_length (this=0x2cdc870,
length=45, strict_p=true) at read.h:309
309           gdb_assert (m_length == length);
(gdb) p m_length
$1 = 56
(gdb) p length
$2 = 45
...

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the Gdb-prs mailing list