--- Begin Message ---
|
Subject: |
Breakage on amd64 when built with -O1 and higher |
|
Date: |
Sat, 9 Jan 2016 14:47:21 +0100 |
|
User-agent: |
Mutt/1.5.24 (2015-08-30) |
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)address@hidden:/tmp/GNUTLS/gnutls-3.3.20$ cd guile/tests
(sid)address@hidden:/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'
--- End Message ---
--- Begin Message ---
|
Subject: |
Re: bug#22337: Breakage on amd64 when built with -O1 and higher |
|
Date: |
Tue, 28 Feb 2017 15:45:24 +0100 |
|
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) |
On Sun 07 Aug 2016 13:19, Andy Wingo <address@hidden> writes:
> On Sat 09 Jan 2016 15:57, address@hidden (Ludovic Courtès) writes:
>
>> Andreas Metzler <address@hidden> skribis:
>>
>>> Debian used to build guile-2.0 without optimization, after changing to
>>> -O2 random segfaults in guile-gnutls testsuite started to appear on
>>> amd64.
>>
>> Are you sure the GnuTLS issue has anything to do with that?
>>
>> Guile has always been built with ‘-O2 -g’ by default, and building with
>> ‘-O0’ has never really been supported (the VM engine could eat too much
>> stack space and do silly things.)
>
> Apparently this is still an issue. Debian actually reverted to
> compiling Guile with -O0:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809608
>
> Which is terrible of course. Surely it is a bug in the Guile GnuTLS
> bindings and not in Guile proper. Compiling Guile with -O2 probably
> holds on to less garbage; could it be that GnuTLS is erroneously not
> making its data structures visible?
>From what I can tell, Debian is back to building Guile with -g -O2:
https://buildd.debian.org/status/fetch.php?pkg=guile-2.0&arch=i386&ver=2.0.13%2B1-4&stamp=1481333071&raw=0
Therefore marking this as closed.
Andy
--- End Message ---