From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 123875 invoked by alias); 29 Nov 2019 09:41:10 -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 123700 invoked by uid 48); 29 Nov 2019 09:41:05 -0000 From: "vries at gcc dot gnu.org" To: dwz@sourceware.org Subject: [Bug default/25024] dwz: Multifile temporary files too large 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: enhancement X-Bugzilla-Who: vries at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: 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-q4/txt/msg00100.txt.bz2 https://sourceware.org/bugzilla/show_bug.cgi?id=3D25024 --- Comment #10 from Tom de Vries --- (In reply to Tom de Vries from comment #9) > There are a few things to mention here: > - there is no clear reason why this should be an error, we could also warn > about not being able to add to the temporary files, and continue the > multifile optimization I ran this again using --devel-trace to get a bit more information, and fou= nd out that actually there's no error. The "dwz: Multifile temporary files too large" message is a warning, telling the user in a _very_ indirect way that= dwz switches off multifile optimization and will continue to process the remain= ing files in single-file mode. This is part of a larger issue in dwz where both warnings and errors are generated using a call to 'error', and consequently it's not immediately cl= ear from the source code which is an error and which is a warning. Furthermore, in write_multifile when running into this warning we immediate= ly return with return value 1, suggesting that processing is stopped, but the return value is actually ignored. --=20 You are receiving this mail because: You are on the CC list for the bug.