public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/29381] [gdb, debug-types, debug-names] read.h:309: internal-error: set_length: Assertion `m_length == length' failed.
Date: Tue, 19 Jul 2022 10:02:43 +0000	[thread overview]
Message-ID: <bug-29381-4717-3B0bjZ2vUp@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29381-4717@http.sourceware.org/bugzilla/>

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

--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
Zooming in on the actual assert, we have:
...
#6  0x0000000000714063 in dwarf2_per_cu_data::set_length (this=0x2cf2cd0,
length=34, 
    strict_p=true) at /home/vries/gdb_versions/devel/src/gdb/dwarf2/read.h:309
309           gdb_assert (m_length == length);
(gdb) p m_length
$5 = 12611
(gdb) p this->sect_off
$7 = (unknown: 0x6d)
...

So initially, during index reading we assign length 12611 to the CU at 0x6d,
but during create_all_comp_units we find that it's actually 34, which looks
correct given the TU at offset 0x8f
...
CU table:
[  0] 0x0
[  1] 0x2e
[  2] 0x6d
[  3] 0x31b0
[  4] 0x7d53
[  5] 0x7f0b

TU table:
[  0] 0x8f
[  1] 0x1eb
[  2] 0x371
[  3] 0x4b0
[  4] 0x4f6
[  5] 0x53c
...

The initial 12611 length corresponds to 0x31b0 - 0x6d.

So that looks like another bug, which normally doesn't surface because we
reject the .debug_names index if it has TUs in the .debug_info section.

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

  parent reply	other threads:[~2022-07-19 10:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-19  7:59 [Bug symtab/29381] New: " vries at gcc dot gnu.org
2022-07-19  8:36 ` [Bug symtab/29381] " vries at gcc dot gnu.org
2022-07-19 10:02 ` vries at gcc dot gnu.org [this message]
2022-07-19 10:24 ` vries at gcc dot gnu.org
2022-07-19 11:34 ` vries at gcc dot gnu.org
2022-07-19 13:14 ` vries at gcc dot gnu.org
2022-07-19 16:50 ` vries at gcc dot gnu.org
2022-07-19 17:36 ` vries at gcc dot gnu.org
2022-07-22 21:52 ` vries at gcc dot gnu.org
2022-08-01 12:04 ` vries at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-29381-4717-3B0bjZ2vUp@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).