From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/24341] New: multifile .debug_info section not present
Date: Tue, 01 Jan 2019 00:00:00 -0000 [thread overview]
Message-ID: <bug-24341-11298@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=24341
Bug ID: 24341
Summary: multifile .debug_info section not present
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: ---
Consider a minimal executable test-case 1:
...
$ cat min.c
int
main (void)
{
return 0;
}
$ gcc -g min.c -o 1
...
When self-multifile-dwz-ing, we get:
...
$ cp 1 2
$ dwz -m 3 1 2
dwz: 3: .debug_info section not present
$ echo $?
1
$ readelf -S 1 2 | grep -c "\.gnu_debugaltlink"
0
...
It's correct that the .debug_info section is missing, there's only a .debug_str
debug section:
...
$ readelf -S 3 | grep \]
[Nr] Name Type Address Offset
[ 0] NULL 0000000000000000 00000000
[ 1] .note.gnu.build-i NOTE 0000000000000000 00000040
[ 2] .debug_str PROGBITS 0000000000000000 00000064
[ 3] .shstrtab STRTAB 0000000000000000 000001d0
...
The .debug_info section in the original file is only one compilation unit big:
...
$ readelf -w 1 | grep '(DW_TAG_compile_unit)'
<0><b>: Abbrev Number: 1 (DW_TAG_compile_unit)
...
and dwz just happens not to find anything in the .debug_info to optimize
against in multifile mode.
I only managed to reproduce this on my ubuntu 16.04 laptop, on openSUSE leap
15.0 I get more compilation units and can't reproduce the error message.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2019-03-14 13:59 UTC|newest]
Thread overview: 2+ 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/24341] " vries at gcc dot gnu.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-24341-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).