From: "mliska at suse dot cz" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/27588] dwz: libxul.so: loclistptr attribute, yet no .debug_loc section
Date: Tue, 16 Mar 2021 10:36:01 +0000 [thread overview]
Message-ID: <bug-27588-11298-nOtpcNWZxz@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27588-11298@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27588
--- Comment #2 from Martin Liska <mliska at suse dot cz> ---
All right, so it's likely nasm issue, there's reduced test-case:
$ cat cdef.asm
%define ARCH_X86_64 1
%ifndef public_prefix
%endif
%define WIN64 0
%if WIN64 ; Windows x64 ;=================================================
%if vzeroupper_required
%endif
%endif
%macro BRANCH_INSTR 0-*
%endmacro
%if ARCH_X86_64
%macro DUP4 1-*
%endmacro
ret
%endif ; ARCH_X86_64
$ cat a.c
int main(int argc, char **argv)
{
return 0;
}
$ nasm -o cdef.o -f elf64 -F dwarf cdef.asm && gcc a.c -O2 -g -shared cdef.o -o
x.so && dwz x.so
Apparently, cdef.o contains the section you're seeking for:
$ readelf -SW cdef.o | grep debug_loc
[11] .debug_loc PROGBITS 0000000000000000 0005c0 000000 00
0 0 1
but the final x.so is somehow corrupted it seems:
$ readelf -w x.so >/dev/null
readelf: Warning: Bogus end-of-siblings marker detected at offset e6 in
.debug_info section
readelf: Warning: Bogus end-of-siblings marker detected at offset e7 in
.debug_info section
readelf: Warning: Bogus end-of-siblings marker detected at offset e8 in
.debug_info section
readelf: Warning: Further warnings about bogus end-of-sibling markers
suppressed
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-03-16 10:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 9:17 [Bug default/27588] New: " mliska at suse dot cz
2021-03-16 10:08 ` [Bug default/27588] " vries at gcc dot gnu.org
2021-03-16 10:36 ` mliska at suse dot cz [this message]
2021-03-16 10:38 ` mliska at suse dot cz
2021-03-16 10:49 ` vries at gcc dot gnu.org
2021-03-16 11:12 ` mliska at suse dot cz
2021-03-16 14:21 ` vries at gcc dot gnu.org
2021-03-16 14:23 ` mliska at suse dot cz
2021-05-17 8:57 ` vries at gcc dot gnu.org
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-27588-11298-nOtpcNWZxz@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).