From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/24204] [dwz, low-mem] Couldn't find DIE referenced by DW_OP_GNU_implicit_pointer
Date: Tue, 01 Jan 2019 00:00:00 -0000 [thread overview]
Message-ID: <bug-24204-11298-UaKmOdtPpJ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24204-11298@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=24204
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at redhat dot com
--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
AFAIU, the problem is as follows:
During the first low-mem phase in read_debug_info, we're supposed to read in
all the intercu-referenced DIES, such that they're available during the second
phase.
But in read_debug_info, we're just skipping over the DW_FORM_exprloc that
points to the location list that contains the DW_OP_GNU_implicit_pointer
reference to the DW_TAG_dwarf_procedure DIE:
...
case DW_FORM_exprloc:
len = read_uleb128 (ptr);
form = DW_FORM_block1;
break;
...
And consequently, when we try to access the DIE in checksum_die, it's not
available.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-02-11 17:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 0:00 [Bug default/24204] New: " vries at gcc dot gnu.org
2019-01-01 0:00 ` [Bug default/24204] " vries at gcc dot gnu.org
2019-01-01 0:00 ` vries at gcc dot gnu.org [this message]
2019-01-01 0:00 ` 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-24204-11298-UaKmOdtPpJ@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=dwz@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).