From: "ginggs at debian dot 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-hHONW7L3WQ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25252-11298@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=25252
--- Comment #2 from Graham Inggs <ginggs at debian dot org> ---
> This still exits with 0 on dwz-0.13-branch, so presumably 0.13-3 is
> just some random recent trunk version.
0.13 + cherry-picks from trunk, I believe. Debian's changelog [1] for
reference.
> As for the exit status 1, that's currently the expected result when
> running into the max-die-limit.
Ah, thank you for the explanation. Passing '-L 100000000' to dwz solves my
problem. Is there any reason I should not do this? Or should I try to get
close to the actual number of DIEs?
[1]
https://metadata.ftp-master.debian.org/changelogs/main/d/dwz/unstable_changelog
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-12-07 8:59 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] " vries at gcc dot gnu.org
2019-01-01 0:00 ` vries at gcc dot gnu.org
2019-01-01 0:00 ` ginggs at debian dot org [this message]
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-hHONW7L3WQ@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).