From: "mliska at suse dot cz" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug general/27367] New: readelf: invalid loclists data with -ffat-lto-objects
Date: Mon, 08 Feb 2021 10:45:34 +0000 [thread overview]
Message-ID: <bug-27367-10460@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=27367
Bug ID: 27367
Summary: readelf: invalid loclists data with -ffat-lto-objects
Product: elfutils
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: general
Assignee: unassigned at sourceware dot org
Reporter: mliska at suse dot cz
CC: elfutils-devel at sourceware dot org
Target Milestone: ---
Using the GCC 11 (master) I see the following issue:
$ cat size.i
int main_argc_remaining;
int main_argc() {
int result = 0;
if (main_argc_remaining)
result = 0;
return 0;
}
$ gcc -c -flto -O size.i -g -ffat-lto-objects &&
/home/marxin/Programming/elfutils/src/readelf -aw size.o
...
DWARF section [27] '.debug_loclists' at offset 0x747:
Table at Offset 0x0:
Length: 24
DWARF version: 5
Address size: 8
Segment size: 0
Offset entries: 0
Not associated with a CU.
Offset: c, Index: 0
startx_endx 3, 8
???..
???
(empty)
end_of_list
Offset: 18, Index: c
startx_endx 30, 1f
???..
???
/home/marxin/Programming/elfutils/src/readelf: invalid loclists data
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-02-08 10:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 10:45 mliska at suse dot cz [this message]
2021-02-08 10:47 ` [Bug general/27367] " mliska at suse dot cz
2021-02-08 11:09 ` mliska at suse dot cz
2021-02-08 11:10 ` mliska at suse dot cz
2021-02-08 11:14 ` mark at klomp dot org
2021-11-04 11:14 ` ldv at sourceware dot org
2021-11-04 11:32 ` mark at klomp dot org
2021-11-08 8:48 ` mark at klomp dot org
2021-11-09 18:17 ` mark at klomp dot 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-27367-10460@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@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).