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/29334] [gdb, debug-types, debug-names] segfault in dwarf2_per_objfile::symtab_set_p
Date: Fri, 08 Jul 2022 07:24:31 +0000 [thread overview]
Message-ID: <bug-29334-4717-v8ChO5oPjy@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29334-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29334
--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
Happens because dwarf2_per_objfile::symtab_set_p is called with per_cu ==
nullptr.
This happens the first time we process a DW_IDX_type_unit in
dw2_debug_names_iterator::next:
...
case DW_IDX_type_unit:
/* Don't crash on bad data. */
if (ull >= per_bfd->tu_stats.nr_tus)
{
complaint (_(".debug_names entry has bad TU index %s"
" [in module %s]"),
pulongest (ull),
objfile_name (objfile));
continue;
}
per_cu = per_bfd->get_cu (ull + per_bfd->tu_stats.nr_tus);
break;
...
We have a reference to type unit 14:
...
(gdb) p ull
$2 = 14
...
The CU table in .debug_names contains 6 entries (0-5) and the TU table contains
62 (0-61).
So type unit 14 is a valid index.
We correctly kept track of the number of TUs:
...
(gdb) p per_bfd->tu_stats.nr_tus
$3 = 62
...
And the all_comp_units.size () is 68, which indeed 62 + 6:
...
(gdb) s
dwarf2_per_bfd::get_cu (this=0x3659360, index=76) at
/home/vries/gdb_versions/devel/src/gdb/dwarf2/read.h:401
401 return this->all_comp_units[index].get ();
(gdb) p this->all_comp_units.size ()
$4 = 68
...
However, the index used is 76, which is too big.
Looking at the CU/TU table, we have:
...
CU table:
[ 0] 0x0
[ 1] 0x2e
[ 2] 0x6d
[ 3] 0x8f
[ 4] 0x4db7
[ 5] 0x4f6f
TU table:
[ 0] 0x0
[ 1] 0x15b
[ 2] 0x2e0
...
And:
...
(gdb) p this->all_comp_units[0].get().sect_off
$16 = 0
(gdb) p this->all_comp_units[1].get().sect_off
$17 = (unknown: 0x2e)
(gdb) p this->all_comp_units[2].get().sect_off
$18 = (unknown: 0x6d)
...
and:
...
(gdb) p this->all_comp_units[6].get().sect_off
$19 = 0
(gdb) p this->all_comp_units[7].get().sect_off
$20 = (unknown: 0x15b)
(gdb) p this->all_comp_units[8].get().sect_off
$21 = (unknown: 0x2e0)
...
So, at first glance, it seems the fix should be something like:
...
- per_cu = per_bfd->get_cu (ull + per_bfd->tu_stats.nr_tus);
+ per_cu = per_bfd->get_cu (ull + per_bfd->cu_stats.nr_cus);
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-07-08 7:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 7:04 [Bug symtab/29334] New: " vries at gcc dot gnu.org
2022-07-08 7:24 ` vries at gcc dot gnu.org [this message]
2022-07-08 7:28 ` [Bug symtab/29334] " vries at gcc dot gnu.org
2022-07-08 10:02 ` vries at gcc dot gnu.org
2022-07-08 13:59 ` vries at gcc dot gnu.org
2022-07-08 14:00 ` vries at gcc dot gnu.org
2022-07-12 12:22 ` 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-29334-4717-v8ChO5oPjy@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).