[pkg-gnupg-maint] gnupg2 2.1.19-3 fails to build on s390x with segfault in xcheck

Daniel Kahn Gillmor dkg at fifthhorseman.net
Tue Mar 21 21:32:27 UTC 2017


On Tue 2017-03-21 16:27:28 -0400, Aurelien Jarno wrote:
> On 2017-03-21 14:31, Daniel Kahn Gillmor wrote:
>> I uploaded gnupg2 2.1.19-3 to experimental today, and it's building fine
>> on all the buildd's thus far except for s390x:
>> 
>> https://buildd.debian.org/status/fetch.php?pkg=gnupg2&arch=s390x&ver=2.1.19-3&stamp=1490117075&raw=0
>> 
>> > Making check in openpgp
>> > make[4]: Entering directory '/«PKGBUILDDIR»/build/tests/openpgp'
>> > LC_ALL=C EXEEXT= PATH=../gpgscm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games srcdir=/«PKGBUILDDIR»/build/../tests/openpgp objdir=/«PKGBUILDDIR»/build GPGSCM_PATH=/«PKGBUILDDIR»/build/../tests/gpgscm:/«PKGBUILDDIR»/build/../tests/openpgp /«PKGBUILDDIR»/build/tests/gpgscm/gpgscm \
>> >   run-tests.scm  version.scm enarmor.scm mds.scm decrypt.scm decrypt-multifile.scm decrypt-dsa.scm decrypt-session-key.scm sigs.scm sigs-dsa.scm encrypt.scm encrypt-multifile.scm encrypt-dsa.scm compression.scm seat.scm clearsig.scm encryptp.scm detach.scm detachm.scm armsigs.scm armencrypt.scm armencryptp.scm signencrypt.scm signencrypt-dsa.scm armsignencrypt.scm armdetach.scm armdetachm.scm genkey1024.scm conventional.scm conventional-mdc.scm multisig.scm verify.scm verify-multifile.scm gpgv-forged-keyring.scm armor.scm import.scm import-revocation-certificate.scm ecc.scm 4gb-packet.scm tofu.scm gpgtar.scm use-exact-key.scm default-key.scm export.scm ssh-import.scm ssh-export.scm quick-key-manipulation.scm key-selection.scm delete-keys.scm gpgconf.scm issue2015.scm issue2346.scm issue2417.scm issue2419.scm issue2929.scm issue2941.scm
>> > Makefile:917: recipe for target 'xcheck' failed
>> > make[4]: *** [xcheck] Segmentation fault
>> > make[4]: Leaving directory '/«PKGBUILDDIR»/build/tests/openpgp'
>> > Makefile:543: recipe for target 'check-recursive' failed
>> 
>> I'm not sure why xcheck is segfaulting here, and only on this arch.  Can
>> you try giving it back to s390x to see if it's a repeatable failure?
>
> I just gave it back.

thanks for the giveback, Aurelien.  

weirdly, it seems to have the same problem the second time too.

Back in version 2.1.18-6, we've got no problem on s390x:

make[4]: Entering directory '/«PKGBUILDDIR»/build/tests/gpgscm'
EXEEXT= GPGSCM_PATH=../../../tests/gpgscm \
	./gpgscm ../../../tests/gpgscm/t-child.scm
Testing process and IPC primitives... 
hello world. 
All good. 
make[4]: Leaving directory '/«PKGBUILDDIR»/build/tests/gpgscm'
make[3]: Leaving directory '/«PKGBUILDDIR»/build/tests/gpgscm'
Making check in openpgp
make[3]: Entering directory '/«PKGBUILDDIR»/build/tests/openpgp'
LC_ALL=C EXEEXT= PATH=../gpgscm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games TMP=/tmp srcdir=/«PKGBUILDDIR»/build/../tests/openpgp objdir=/«PKGBUILDDIR»/build GPGSCM_PATH=/«PKGBUILDDIR»/build/../tests/gpgscm:/«PKGBUILDDIR»/build/../tests/openpgp /«PKGBUILDDIR»/build/tests/gpgscm/gpgscm \
  run-tests.scm  version.scm enarmor.scm mds.scm decrypt.scm decrypt-multifile.scm decrypt-dsa.scm decrypt-session-key.scm sigs.scm sigs-dsa.scm encrypt.scm encrypt-multifile.scm encrypt-dsa.scm compression.scm seat.scm clearsig.scm encryptp.scm detach.scm detachm.scm armsigs.scm armencrypt.scm armencryptp.scm signencrypt.scm signencrypt-dsa.scm armsignencrypt.scm armdetach.scm armdetachm.scm genkey1024.scm conventional.scm conventional-mdc.scm multisig.scm verify.scm verify-multifile.scm gpgv-forged-keyring.scm armor.scm import.scm import-revocation-certificate.scm ecc.scm 4gb-packet.scm tofu.scm gpgtar.scm use-exact-key.scm default-key.scm export.scm ssh-import.scm ssh-export.scm quick-key-manipulation.scm key-selection.scm delete-keys.scm issue2015.scm issue2346.scm issue2417.scm issue2419.scm
PASS: setup.scm 
Printing the GPG version 
PASS: version.scm


but since the upgrade to 2.1.19-3 in experimental, we're seeing the the
segfault on s390x.

I'm not even sure how to interpret the error message: is it saying that
make itself Segfaulted, or that gpgscm segfaulted?

I've connected to zelenka to try to reproduce the problem directly on
s390x but i haven't been able to get there yet.

Any pointers or things i should be aware of for s390x (i'm not used to
this architecture) would be welcome.

      --dkg



More information about the pkg-gnupg-maint mailing list