From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/25459] New: Forward pseudo-reference triggers error
Date: Wed, 01 Jan 2020 00:00:00 -0000 [thread overview]
Message-ID: <bug-25459-11298@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=25459
Bug ID: 25459
Summary: Forward pseudo-reference triggers error
Product: dwz
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: default
Assignee: nobody at sourceware dot org
Reporter: vries at gcc dot gnu.org
CC: dwz at sourceware dot org
Target Milestone: ---
As we have seen, the test-case in PR25456 triggers an error:
...
$ dwz clang-offload-bundler-10.debug
dwz: clang-offload-bundler-10.debug: Couldn't find DIE referenced by
DW_OP_GNU_implicit_pointer
...
However, the question is: should this error be triggered?
We have a DIE in a partial unit:
...
<3><481a37>: Abbrev Number: 1 (DW_TAG_formal_parameter)
<481a38> DW_AT_abstract_origin: <0x5232>
<481a3c> DW_AT_location : 0x902527 (location list)
<481a40> DW_AT_GNU_locviews: 0x902525
...
for which we calculate the checksum, so we follow the DW_AT_location to:
...
00902525 v000000000000000 v000000000000003 location view pair
00902527 v000000000000000 v000000000000003 views at 00902525 for:
0000000000000033 0000000000000033 (DW_OP_GNU_implicit_pointer:
<0x1263f86> 0)
...
from where we would like to go to:
...
<1><1263f86>: Abbrev Number: 206 (DW_TAG_dwarf_procedure)
<1263f88> DW_AT_location : 4 byte block: 9e 2 7e 0
(DW_OP_implicit_value 2 byte block: 7e 0 )
...
but we can't because the CU containing this DIE hasn't been processed by
read_debug_info.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-01-24 19:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-01 0:00 vries at gcc dot gnu.org [this message]
2020-01-01 0:00 ` [Bug default/25459] " vries at gcc dot gnu.org
2021-03-12 10:56 ` 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-25459-11298@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).