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-OIYqvWnXZV@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24766-11298@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=24766
--- Comment #10 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Matthias Klose from comment #9)
> that's the Debian issue connected with this issue:
>
> https://bugs.debian.org/931792
>
> for the error codes: compressed debug info maybe should have an error code
> which shows that it can be ignored? same for code not built with -g?
So, AFAIU, you mean something along the lines of:
...
$ dwz 1; echo $?
0
$ dwz 1; echo $?
dwz: 1: DWARF compression not beneficial
2
$ dwz 2; echo $?
dwz: 2: .debug_info section not present
3
$ dwz 3; echo $?
dwz: 3: invalid dwarf: no DIE at reference 0x123
4
...
That is, we let the exit status be informative about what type of situations we
find, and let the caller decide how to handle these.
We could do something like that, but that looks like an enhancement for a next
release to me, not a regression fix. I'll file this as spin-off PR.
For now, let's fix this regression more pragmatically.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-07-11 10:13 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 ` vries at gcc dot gnu.org [this message]
2019-01-01 0:00 ` [Bug default/24766] [Regression] doko at debian dot org
2019-01-01 0:00 ` doko at debian dot org
2019-01-01 0:00 ` 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 ` 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 jakub at redhat dot com
2019-01-01 0:00 ` [Bug default/24766] [Regression] vries at gcc dot gnu.org
2019-01-01 0:00 ` costamagnagianfranco at yahoo dot it
2019-01-01 0:00 ` doko at debian dot org
2019-01-01 0:00 ` vries at gcc dot gnu.org
2019-01-01 0:00 ` jakub at redhat dot com
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-OIYqvWnXZV@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).