From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7539 invoked by alias); 11 Jul 2019 10:55:15 -0000 Mailing-List: contact dwz-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Post: List-Help: List-Subscribe: Sender: dwz-owner@sourceware.org Received: (qmail 7494 invoked by uid 48); 11 Jul 2019 10:55:11 -0000 From: "vries at gcc dot gnu.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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: dwz X-Bugzilla-Component: default X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: vries at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: nobody at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2019-q3/txt/msg00075.txt.bz2 https://sourceware.org/bugzilla/show_bug.cgi?id=3D24766 --- Comment #13 from Tom de Vries --- (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 benefici= al, > another one has corrupt .debug_info, etc. I suppose you could classify the exit status in increasing level of severit= y, 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 ] --=20 You are receiving this mail because: You are on the CC list for the bug.