public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/26813] DW_FORM_rnglistx and DW_FORM_loclistx not fully supported
Date: Mon, 16 May 2022 01:12:07 +0000 [thread overview]
Message-ID: <bug-26813-4717-NmZQNm9JTJ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26813-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=26813
--- Comment #21 from Simon Marchi <simark at simark dot ca> ---
(In reply to Jean-Michaël Celerier from comment #19)
> Thanks Tom, do you know if there is a tool I could use to have an idea of
> where in the code things go wrong ? e.g. the error I'm getting is:
>
> DW_FORM_rnglistx index pointing outside of .debug_rnglists offset array
After this message, there should normally be a "[in module %s]" part telling
you at least in which object file this is.
> if I could see at least in which file and ideally which function these
> DW_FORM_rnglistx get generated that would be very helpful for making a repro
We could include in those messages which CU (DW_AT_compile_unit) GDB was
reading when encountering the problem, and probably the offset of the DIE too.
Would that help?
It's possible that you encountered some other bug in GDB, or it's possible you
found some compiler bug. The only way to know is to dig in the DWARF, really.
As Tom said, can you please file a new bug, with a reproducer?
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2022-05-16 1:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 17:30 [Bug symtab/26813] New: " zoran.zaric at amd dot com
2020-10-29 17:33 ` [Bug symtab/26813] " zoran.zaric at amd dot com
2020-10-29 18:08 ` simark at simark dot ca
2020-10-30 14:22 ` tromey at sourceware dot org
2020-10-30 15:03 ` zoran.zaric at amd dot com
2020-10-30 18:21 ` simark at simark dot ca
2020-10-30 18:22 ` simark at simark dot ca
2020-10-30 19:03 ` simark at simark dot ca
2020-10-30 21:19 ` simark at simark dot ca
2020-11-02 15:57 ` simark at simark dot ca
2021-01-20 9:26 ` mliska at suse dot cz
2021-02-02 15:42 ` cvs-commit at gcc dot gnu.org
2021-02-02 15:43 ` cvs-commit at gcc dot gnu.org
2021-02-02 15:43 ` cvs-commit at gcc dot gnu.org
2021-02-02 15:43 ` cvs-commit at gcc dot gnu.org
2021-02-02 15:43 ` simark at simark dot ca
2021-02-03 19:17 ` cvs-commit at gcc dot gnu.org
2021-02-03 19:17 ` cvs-commit at gcc dot gnu.org
2021-02-03 19:17 ` cvs-commit at gcc dot gnu.org
2022-05-15 12:13 ` jeanmichael.celerier at gmail dot com
2022-05-15 14:33 ` tromey at sourceware dot org
2022-05-15 14:55 ` jeanmichael.celerier at gmail dot com
2022-05-15 15:09 ` tromey at sourceware dot org
2022-05-16 1:12 ` simark at simark dot ca [this message]
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-26813-4717-NmZQNm9JTJ@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).