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: Mon, 07 Sep 2020 07:53:02 +0000 [thread overview]
Message-ID: <bug-24251-11298-kpStVtJad2@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24251-11298@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=24251
Mark Wielaard <mark at klomp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|FIXED |---
Status|RESOLVED |REOPENED
CC| |mark at klomp dot org
--- Comment #11 from Mark Wielaard <mark at klomp dot org> ---
Note that there are multiple warnings in that log:
warning: Unsupported auto-load script at offset 0 in section .debug_gdb_scripts
of file
/builddir/build/BUILDROOT/sysutil-0-0.3.20200615git15668db.fc33.x86_64/usr/bin/boottime.
Use `info auto-load python-scripts [REGEXP]' to list them.
nm:
/builddir/build/BUILDROOT/sysutil-0-0.3.20200615git15668db.fc33.x86_64/usr/bin/boottime:
.gnu.version_r invalid entry
nm:
/builddir/build/BUILDROOT/sysutil-0-0.3.20200615git15668db.fc33.x86_64/usr/bin/boottime:
no symbols
dwz: Allocatable section in
./usr/bin/boottime-0-0.3.20200615git15668db.fc33.x86_64.debug after
non-allocatable ones
It is a golang binary and seems to use both the golang linker and the system
linker. I suspect that it really is slightly corrupt because of that.
Note that the section offsets jump around a bit:
Section Headers:
[Nr] Name Type Addr Off Size ES
Flags Lk Inf Al
[ 0] NULL 0000000000000000 00000000 00000000 0
0 0 0
[ 1] .text PROGBITS 0000000000401000 00001000 000ab22e 0 AX
0 0 32
[ 2] .plt PROGBITS 00000000004ac230 000ac230 00000010 16 AX
0 0 16
[ 3] .rodata PROGBITS 00000000004ad000 000ad000 00020123 0 A
0 0 32
[ 4] .gnu.version_r GNU_verneed 00000000004cd123 000cd123 00000000 0 A
8 0 1
[ 5] .dynsym DYNSYM 0000000000526970 00126970 00000018 24 A
8 1 8
[ 6] .rela RELA 00000000004cd128 000cd128 00059820 24 A
5 0 8
[ 7] .rela.plt RELA 0000000000526948 00126948 00000000 24 AI
5 17 8
[ 8] .dynstr STRTAB 0000000000526948 00126948 00000001 0 A
0 0 1
[ 9] .gnu.version GNU_versym 000000000052694a 0012694a 00000002 2 A
5 0 2
[10] .hash HASH 0000000000526950 00126950 00000014 4 A
5 0 8
[11] .data.rel.ro PROGBITS 0000000000527000 00127000 00027f40 0 WA
0 0 32
[12] .data.rel.ro.typelink PROGBITS 000000000054ef40 0014ef40 000007a4 0
WA 0 0 32
[13] .data.rel.ro.itablink PROGBITS 000000000054f6e8 0014f6e8 00000070 0
WA 0 0 8
[14] .data.rel.ro.gosymtab PROGBITS 000000000054f758 0014f758 00000000 0
WA 0 0 1
[15] .data.rel.ro.gopclntab PROGBITS 000000000054f760 0014f760 00068900 0
WA 0 0 32
[16] .go.buildinfo PROGBITS 00000000005b9000 001b9000 00000020 0 WA
0 0 16
[17] .got.plt PROGBITS 00000000005b9020 001b9020 00000018 8 WA
0 0 8
[18] .dynamic DYNAMIC 00000000005b9040 001b9040 000000b0 16 WA
8 0 8
[19] .got PROGBITS 00000000005b90f0 001b90f0 00000000 8 WA
0 0 8
[20] .noptrdata PROGBITS 00000000005b9100 001b9100 0000e740 0 WA
0 0 32
[21] .data PROGBITS 00000000005c7840 001c7840 000076d0 0 WA
0 0 32
[22] .bss NOBITS 00000000005cef20 001cef10 00030050 0 WA
0 0 32
[23] .noptrbss NOBITS 00000000005fef80 001cef10 00002888 0 WA
0 0 32
[24] .tbss NOBITS 0000000000000000 001cef10 00000008 0
WAT 0 0 8
[25] .interp PROGBITS 0000000000400fe4 00000fe4 0000001c 0 A
0 0 1
[26] .note.gnu.build-id NOTE 0000000000400fc0 00000fc0 00000024 0 A
0 0 4
[27] .note.go.buildid NOTE 0000000000400f5c 00000f5c 00000064 0 A
0 0 4
[28] .gnu_debuglink PROGBITS 0000000000000000 001cef10 00000038 0
0 0 4
[29] .gnu_debugdata PROGBITS 0000000000000000 001cef48 00004624 0
0 0 1
[30] .shstrtab STRTAB 0000000000000000 001d356c 00000156 0
0 0 1
In particular .intrp (25), .note.gnu.build-id (26) and .note.go.buildid (27)
have offsets that place them at the start of the file instead of at the end.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-09-07 7:53 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 [this message]
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
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-kpStVtJad2@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).