From: Rob Browning <rlb@defaultvalue.org>
To: 29884@debbugs.gnu.org
Subject: bug#29884: Appears -fstack-protector-strong can cause the test-out-of-memory crashes
Date: Thu, 28 Dec 2017 18:19:50 -0600 [thread overview]
Message-ID: <87r2re8jx5.fsf@trouble.defaultvalue.org> (raw)
While updating Debian to 2.2.3 (and trying to get 2.2 building on all
the release architectures) I hit the previously reported
test-out-of-memory failure, or something similar.
I spent a while poking at it, and it looks like -fstack-protector-strong
can reliably cause the crash.
Additional details: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=+29464#11
Thanks
--
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
next reply other threads:[~2017-12-29 0:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-29 0:19 Rob Browning [this message]
2017-12-29 0:45 ` bug#29884: Appears -fstack-protector-strong can cause the test-out-of-memory crashes Rob Browning
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r2re8jx5.fsf@trouble.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=29884@debbugs.gnu.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).