From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/24251] New: Allocatable section after non-allocatable ones
Date: Tue, 01 Jan 2019 00:00:00 -0000 [thread overview]
Message-ID: <bug-24251-11298@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=24251
Bug ID: 24251
Summary: Allocatable section after non-allocatable ones
Product: dwz
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: default
Assignee: nobody at sourceware dot org
Reporter: vries at gcc dot gnu.org
CC: dwz at sourceware dot org
Target Milestone: ---
[ This is essentially a refiling of PR21191 - "objcopy --only-keep-debug
creates non-monotonically increasing section offsets", which was closed as
WONTFIX, for dwz. ]
For the example from PR21191, with trunk dwz and objcopy we have:
...
$ cat t.c
int main()
{
}
$ gcc t.c -g
$ objcopy --only-keep-debug a.out a.debug
$ dwz a.debug
dwz: Allocatable section in a.debug after non-allocatable ones
...
The dwz tool complains that allocatable section .init_array at offset 0xe40:
...
[17] .init_array NOBITS 0000000000600e40 00000e40
0000000000000008 0000000000000008 WA 0 0 8
...
is at a bigger offset than non-allocatable section .debug_info at offset 0x410:
...
[26] .debug_info PROGBITS 0000000000000000 00000410
00000000000002f3 0000000000000000 0 0 1
...
In the original a.out this situation does not occur:
...
[17] .init_array INIT_ARRAY 0000000000600e40 00000e40
0000000000000008 0000000000000008 WA 0 0 8
[26] .debug_info PROGBITS 0000000000000000 000011a0
00000000000002f3 0000000000000000 0 0 1
...
The rationale with which PR21191 was closed as WONTFIX is: "File offset for a
SHT_NOBITS section is irrelevant".
Following that rationale, dwz should not complain here.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2019-02-20 14:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 0:00 vries at gcc dot gnu.org [this message]
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
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@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).