From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/27767] dwz: libxul.so.debug: Unknown DWARF DW_OP_xderef_type
Date: Fri, 13 Jan 2023 14:32:24 +0000 [thread overview]
Message-ID: <bug-27767-11298-9fF2QbclNY@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27767-11298@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27767
--- Comment #4 from Mark Wielaard <mark at klomp dot org> ---
This might be a bug in NASM because this is the bogus compile unit:
<0><4ac969e7>: Abbrev Number: 1 (DW_TAG_compile_unit)
<4ac969e8> DW_AT_low_pc : 0x4b17c00
<4ac969f0> DW_AT_high_pc : 0x4b1b9f7
<4ac969f8> DW_AT_stmt_list : 0x621f999
<4ac969fc> DW_AT_name :
/home/abuild/rpmbuild/BUILD/firefox-87.0/third_party/dav1d/src/x86/cdef_avx2.asm
<4ac96a4d> DW_AT_producer : NASM 2.15.05
<4ac96a5a> DW_AT_language : 32769 (MIPS assembler)
<1><4ac96a5c>: Abbrev Number: 2 (DW_TAG_subprogram)
<4ac96a5d> DW_AT_low_pc : 0x4b17c00
<4ac96a65> DW_AT_frame_base : 0x0 (location list)
<1><4ac96a69>: Abbrev Number: 0
<0><4ac96a6a>: Abbrev Number: 0
readelf: ./libxul.so.debug: Warning: Bogus end-of-siblings marker detected at
offset 4ac96a6a in .debug_info section
readelf: ./libxul.so.debug: Warning: Further warnings about bogus
end-of-sibling markers suppressed
<-1><4ac96a6b>: Abbrev Number: 0
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-01-13 14:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-22 11:35 [Bug default/27767] New: " mliska at suse dot cz
2021-08-06 1:33 ` [Bug default/27767] " lennordocdoc0921 at gmail dot com
2023-01-13 8:36 ` mliska at suse dot cz
2023-01-13 14:17 ` mark at klomp dot org
2023-01-13 14:32 ` mark at klomp dot org [this message]
2023-01-16 10:14 ` mliska at suse dot cz
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-27767-11298-9fF2QbclNY@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).