From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/25252] dwz: returns exit status 1, causing FTBFS in deal.ii
Date: Tue, 01 Jan 2019 00:00:00 -0000 [thread overview]
Message-ID: <bug-25252-11298-VdW7WGGDlO@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25252-11298@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=25252
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |UNCONFIRMED
CC| |vries at gcc dot gnu.org
Ever confirmed|1 |0
--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
This still exits with 0 on dwz-0.13-branch, so presumably 0.13-3 is just some
random recent trunk version.
I've bisected this on trunk to commit 48a78ec "Improve handling of running into
both low-mem and max die-limits".
The commit makes the first dwz here return 1, which makes thisret 1, which
makes ret 1, which gets us an exit status of 1:
...
thisret = (low_mem_die_limit == 0
? 2
: dwz (file, NULL, &resa[i - optind],
hardlinks ? resa : NULL, &argv[optind]));
if (thisret == 2)
{
multifile_mode = MULTIFILE_MODE_LOW_MEM;
thisret = dwz (file, NULL, &resa[i - optind],
hardlinks ? resa : NULL, &argv[optind]);
}
else if (resa[i - optind].res == 0)
successcount++;
else if (thisret == 1)
ret = 1;
...
Without the commit, the second dwz returns 1, which is ignored, which is a bug,
which should be fixed by this patch:
...
diff --git a/dwz.c b/dwz.c
index 313c317..af891ab 100644
--- a/dwz.c
+++ b/dwz.c
@@ -13525,7 +13525,7 @@ main (int argc, char *argv[])
}
else if (resa[i - optind].res == 0)
successcount++;
- else if (thisret == 1)
+ if (thisret == 1)
ret = 1;
if (hardlink
&& resa[i - optind].res >= 0
...
As for the exit status 1, that's currently the expected result when running
into the max-die-limit.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-12-06 14:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 0:00 [Bug default/25252] New: " ginggs at debian dot org
2019-01-01 0:00 ` [Bug default/25252] " ginggs at debian dot org
2019-01-01 0:00 ` vries at gcc dot gnu.org [this message]
2019-01-01 0:00 ` vries at gcc dot gnu.org
2021-02-18 23:55 ` mark at klomp dot org
2021-03-02 12:11 ` vries at gcc dot gnu.org
2021-03-04 9:01 ` vries at gcc dot gnu.org
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-25252-11298-VdW7WGGDlO@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).