From: Andreas Metzler <ametzler@bebt.de>
To: 22337@debbugs.gnu.org
Cc: "Ludovic Courtès" <ludo@gnu.org>
Subject: bug#22337: Breakage on amd64 when built with -O1 and higher
Date: Sat, 9 Jan 2016 14:47:21 +0100 [thread overview]
Message-ID: <20160109134721.GD1241@argenau.bebt.de> (raw)
Hello,
this is <https://bugs.debian.org/809608>:
Debian used to build guile-2.0 without optimization, after changing to
-O2 random segfaults in guile-gnutls testsuite started to appear on
amd64.
This is easily reproducible by building gnutls 3.3.x (18, 19, 20
tested) on amd64 and running the guile testsuite until it fails:
(sid)ametzler@argenau:/tmp/GNUTLS/gnutls-3.3.20$ cd guile/tests
(sid)ametzler@argenau:/tmp/GNUTLS/gnutls-3.3.20/guile/tests$ j=0 ; rm openpgp-auth.scm.log openpgp-auth.scm.trs test-suite.log ; while make test-suite.log TEST_LOGS=openpgp-auth.scm.log ; do j=$(($j+1)) ; sleep .01 ; rm openpgp-auth.scm.log openpgp-auth.scm.trs test-suite.log ; done ; echo xxx $j
This will usually be the case after run #1 or #2.
The issue not Debian specific, I also see this with GIT stable-2.0.
Both Ludovic and me have managed to generate backtraces:
http://article.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/8372
http://article.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/8379
cu Andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
next reply other threads:[~2016-01-09 13:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-09 13:47 Andreas Metzler [this message]
2016-01-09 14:57 ` bug#22337: Breakage on amd64 when built with -O1 and higher Ludovic Courtès
2016-01-09 15:45 ` Andreas Metzler
2016-08-07 11:19 ` Andy Wingo
2017-02-28 14:45 ` Andy Wingo
2017-02-28 16:37 ` Andreas Metzler
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=20160109134721.GD1241@argenau.bebt.de \
--to=ametzler@bebt.de \
--cc=22337@debbugs.gnu.org \
--cc=ludo@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).