From: "jakub at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/29637] dzw fails with Unknown DWARF DW_OP_255
Date: Thu, 29 Sep 2022 18:15:58 +0000 [thread overview]
Message-ID: <bug-29637-11298-QUBK6UTLKY@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29637-11298@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29637
Jakub Jelinek <jakub at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at redhat dot com
--- Comment #2 from Jakub Jelinek <jakub at redhat dot com> ---
This is while processing of
<10><16d34>: Abbrev Number: 12 (DW_TAG_variable)
<16d35> DW_AT_abstract_origin: <0x63976>
<16d39> DW_AT_location : 0x29d51 (location list)
<16d3d> DW_AT_GNU_locviews: 0x29d47
and seems even readelf -wo shows total garbage for that:
00029d51 v000000000000001 v000000000000000 views at 00029d47 for:
000000000000af34 000000000000b10b (DW_OP_implicit_value 16 byte
block: ff ff ff ff ff ff ff ff 30 b1 0 0 0 0 0 0 )
00029d75 v000000000000000 v000000000000000 views at 00029d49 for:
000000000000b161 ffffffff109e0012 ((User defined location op
0xff))
00039d86 v000000000000000 v000000000000000 views at 00029d4b for:
e201000000000000 e2000000000000cb ((Unknown location op 0x0))
(start > end)
00039e63 v000000000000000 v000000000000000 views at 00029d4d for:
d64e9f7b80910004 d686000000000000 ()
00039e75 v000000000000000 v000000000000000 views at 00029d4f for:
8091000400000000 0000000000009f7b () (start > end)
00039e87 v000000000000034 v00000000000002f views at 00029d51 for:
0000000000000000 0000cc1100000001 ()
00039e99 v000000000000000 v000000000000000 views at 00029d54 for:
00000000cc480000 00d64e5e00010000 ()
00039eab v000000000000000 v000000000000000 views at 00029d56 for:
000000d686000000 00005e0001000000 ()
00039ebd v000000000000000 v00000000000000b views at 00029d58 for:
0000000000000000 0000000100000000 ((Unknown location op 0x0))
00046ae0 v000000000000031 v000000000000000 views at 00029d5a for:
0000000000000000 0000436000000000 ()
00046af2 v000000000000000 v000000000000000 views at 00029d5d for:
0000000043690000 0043695500010000 ()
00046b04 v000000000000000 v000000000000000 views at 00029d5f for:
000000436e000000 436e560001000000 ()
00046b16 v000000000000012 v000000000000000 views at 00029d61 for:
0000437300000000 7355000100000000 ((Unknown location op 0x0))
00046b6b v00000000000081e v30ffffffffffffff views at 00029d63 for:
00000000004fe100 00004fe154000100 ()
00046b7d v000000000000031 v000000000000000 views at 00029d6e for:
000000004fe20000 9f5501f300040000 ()
00046b8f <End of list>
Bet GCC emitted there DW_OP_implicit_value 16 with just 8 bytes of data after
it.
I vaguely remember fixing some issues like this, I think e.g.
https://gcc.gnu.org/PR99562 and
https://gcc.gnu.org/PR103046
Anyway, doesn't seem like a dwz bug to me.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2022-09-29 18:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 8:33 [Bug default/29637] New: " nolange79 at gmail dot com
2022-09-29 11:27 ` [Bug default/29637] " mliska at suse dot cz
2022-09-29 18:15 ` jakub at redhat dot com [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-29637-11298-QUBK6UTLKY@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).