From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/24251] Allocatable section after non-allocatable ones
Date: Thu, 24 Sep 2020 22:18:21 +0000 [thread overview]
Message-ID: <bug-24251-11298-783PUAxbJN@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24251-11298@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=24251
--- Comment #15 from Mark Wielaard <mark at klomp dot org> ---
(In reply to Mark Wielaard from comment #14)
> Created attachment 12847 [details]
> boottime-debug
>
> Got one, extracted from
> https://koji.fedoraproject.org/koji/buildinfo?buildID=1570316
> sysutil-debuginfo-0-0.3.20200615git15668db.fc33.x86_64.rpm
And dwz is right, it really has an allocated section in between non-allocated
ones:
[33] .debug_ranges PROGBITS 000000000067e88f 0017edfd 00034d10 0
0 0 1
[34] .interp NOBITS 0000000000400fe4 001b3b0d 0000001c 0 A
0 0 1
[35] .note.gnu.build-id NOTE 0000000000400fc0 001b3b10 00000024 0 A
0 0 4
[36] .note.go.buildid NOTE 0000000000400f5c 001b3b34 00000064 0 A
0 0 4
[37] .gdb_index PROGBITS 0000000000000000 001b3b98 0004321f 0
0 0 1
We can (and I believe dwz does) ignore the .interp section, since that is
NOBITS. But those two build-id/buildid NOTEs are allocated in the middle of the
file and so cannot be moved. This looks like a broken ELF file to begin with.
Those sections really should have been at the start of the file. I wonder if
this is a bug in the golang toolchain. If so, it would be better to fix that
than to try work around it.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-09-24 22:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 0:00 [Bug default/24251] New: " vries at gcc dot gnu.org
2019-01-01 0:00 ` [Bug default/24251] " vries at gcc dot gnu.org
2019-01-01 0:00 ` vries at gcc dot gnu.org
2019-01-01 0:00 ` vries at gcc dot gnu.org
2019-01-01 0:00 ` vries at gcc dot gnu.org
2019-01-01 0:00 ` vries at gcc dot gnu.org
2019-01-01 0:00 ` vries at gcc dot gnu.org
2019-01-01 0:00 ` vries at gcc dot gnu.org
2019-01-01 0:00 ` vries at gcc dot gnu.org
2019-01-01 0:00 ` vries at gcc dot gnu.org
2020-09-06 19:28 ` jan.kratochvil at redhat dot com
2020-09-07 7:53 ` mark at klomp dot org
2020-09-07 8:01 ` jan.kratochvil at redhat dot com
2020-09-08 13:27 ` vries at gcc dot gnu.org
2020-09-17 15:51 ` mark at klomp dot org
2020-09-24 22:18 ` mark at klomp dot org [this message]
2020-09-25 7:56 ` jan.kratochvil at redhat dot com
2020-09-25 8:03 ` jakub at redhat dot com
2020-09-25 9:44 ` mark at klomp dot org
2020-09-25 9:52 ` jan.kratochvil at redhat dot com
2020-09-25 18:49 ` mark at klomp dot org
2021-02-13 23:05 ` 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-24251-11298-783PUAxbJN@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).