From: "jakub at redhat dot com" <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-tWRMzD9Qqx@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 #5 from Jakub Jelinek <jakub at redhat dot com> ---
Unsure what people want. E.g. the rpm find-debuginfo.sh I think just ignores
the return status of dwz, the program should either perform the compression if
beneficial and possible, or give up, but neither case is some kind of error.
The only "errors" are dwz assertion failures and even those should hopefully
not break stuff, just worse case keep it uncompressed.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2019-07-04 15:09 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] vries at gcc dot gnu.org
2019-01-01 0:00 ` 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] 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 ` vries at gcc dot gnu.org
2019-01-01 0:00 ` jakub at redhat dot com [this message]
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-tWRMzD9Qqx@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).