public inbox for dwz@sourceware.org
 help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/24766] [Regression] dwz exits with 1 when running into ".debug_info section not present" error
Date: Tue, 01 Jan 2019 00:00:00 -0000	[thread overview]
Message-ID: <bug-24766-11298-3n5vopD93w@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 #13 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #12)
> And then the question is what happens if there are multiple issues (or
> harmless warnings) reported, what the final error code should be.  Say -m,
> one file has no .debug_info, another one where no compression is beneficial,
> another one has corrupt .debug_info, etc.

I suppose you could classify the exit status in increasing level of severity,
and return the maximum severity.

Something like:
- 0: valid input, compressed
- 1: valid input, not compressed
- 2: invalid input, compressed
- 3: invalid input, not compressed
[ Though I'm not sure about the relative order of 1 and 2 ]

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2019-07-11 10:55 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] 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 [this message]
2019-01-01  0:00 ` [Bug default/24766] [Regression] 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 ` 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 ` 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
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

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-3n5vopD93w@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).