From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/24766] [Regression]
Date: Tue, 01 Jan 2019 00:00:00 -0000 [thread overview]
Message-ID: <bug-24766-11298-tKdW2Cwzca@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24766-11298@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=24766
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at redhat dot com
--- Comment #4 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Matthias Klose from comment #3)
> updated: https://people.debian.org/~doko/tmp/tst-v.tar.xz
So, the error is:
...
$ ./run.sh
+ cp verilator_bin 1
+ cp verilator_bin_dbg 2
+ cp verilator_coverage_bin_dbg 3
+ dwz -m 4 1 2 3
dwz: 1: .debug_info section not present
dwz: 2: DWARF compression not beneficial - old size 44630638 new size 44641594
+ echo 'exit status: 1'
exit status: 1
...
This is fallout of 815ac61 "Honour errors when processing more than one file".
If we run dwz on an executable without .debug_info section, we get an exit
status of 1:
...
$ dwz verilator_bin; echo $?
dwz: verilator_bin: .debug_info section not present
1
...
However, before the 815ac61 commit, if we did the same in multifile mode, we
got an exit status of 0:
...
$ cp verilator_bin 1
$ cp 1 2
$ dwz -m 3 1 2; echo $?
dwz: 1: .debug_info section not present
dwz: 2: .debug_info section not present
dwz: Too few files for multifile optimization
0
...
After the 815ac61 commit, we get an exit status of 1, just as in regular mode:
...
$ dwz -m 3 1 2; echo $?
dwz: 1: .debug_info section not present
dwz: 2: .debug_info section not present
dwz: Too few files for multifile optimization
1
...
Jakub, WDYT? We could argue that not having .debug_info (due to an executable
not being compiled with -g) is not worth exiting with 1 for.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-07-04 15:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 0:00 [Bug default/24766] New: [Regression] doko at debian dot org
2019-01-01 0:00 ` [Bug default/24766] [Regression] doko at debian dot 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 ` doko at debian dot org
2019-01-01 0:00 ` [Bug default/24766] [Regression] dwz exits with 1 when running into ".debug_info section not present" error vries at gcc dot gnu.org
2019-01-01 0:00 ` [Bug default/24766] [Regression] vries at gcc dot gnu.org
2019-01-01 0:00 ` [Bug default/24766] [Regression] dwz exits with 1 when running into ".debug_info section not present" error vries at gcc dot gnu.org
2019-01-01 0:00 ` jakub at redhat dot com
2019-01-01 0:00 ` [Bug default/24766] [Regression] jakub at redhat dot com
2019-01-01 0:00 ` doko at debian dot org
2019-01-01 0:00 ` costamagnagianfranco at yahoo dot it
2019-01-01 0:00 ` vries at gcc dot gnu.org [this message]
2019-01-01 0:00 ` 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-24766-11298-tKdW2Cwzca@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).