GNU bug report logs - #34484
GCL: segfault on invocation on x86_64 and i686

Previous Next

Package: guix;

Reported by: Diego Nicola Barbato <dnbarbato <at> posteo.de>

Date: Fri, 15 Feb 2019 08:42:02 UTC

Severity: normal

Done: Diego Nicola Barbato <dnbarbato <at> posteo.de>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Diego Nicola Barbato <dnbarbato <at> posteo.de>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#34484: closed (GCL: segfault on invocation on x86_64 and i686)
Date: Fri, 27 Sep 2019 07:01:01 +0000
[Message part 1 (text/plain, inline)]
Your message dated Fri, 27 Sep 2019 09:00:29 +0200
with message-id <87ef02gr5e.fsf <at> GlaDOS.home>
and subject line Re: GCL: segfault on invocation on x86_64 and i686
has caused the debbugs.gnu.org bug report #34484,
regarding GCL: segfault on invocation on x86_64 and i686
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
34484: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=34484
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
From: Diego Nicola Barbato <dnbarbato <at> posteo.de>
To: bug-guix <at> gnu.org
Subject: GCL: segfault on invocation on x86_64 and i686
Date: Fri, 15 Feb 2019 09:29:31 +0100
Hello Guix,

GCL segfaults upon execution on x86_64 and i686.  This is most likely
the reason why Maxima fails to build on those architectures [0] [1].

This is what I tried:

--8<---------------cut here---------------start------------->8---

diego <at> GLaDOS ~$ guix build gcl
/gnu/store/5zzfw856c1acrmalsdznm1093mkvnwls-gcl-2.6.12-2.d3335e2
diego <at> GLaDOS ~$ /gnu/store/5zzfw856c1acrmalsdznm1093mkvnwls-gcl-2.6.12-2.d3335e2/bin/gcl
Speicherzugriffsfehler
diego <at> GLaDOS ~$ guix build -s i686-linux gcl
/gnu/store/cbw0k4apa6qiqfm7g9j0lzfbzfk6mxj2-gcl-2.6.12-2.d3335e2
diego <at> GLaDOS ~$ /gnu/store/cbw0k4apa6qiqfm7g9j0lzfbzfk6mxj2-gcl-2.6.12-2.d3335e2/bin/gcl
Speicherzugriffsfehler

--8<---------------cut here---------------end--------------->8---

I also tried building GCL locally to check if this was something
non-deterministic with the same result:

--8<---------------cut here---------------start------------->8---

diego <at> GLaDOS ~$ guix build gcl --check --keep-failed

[...]

phase `compress-documentation' succeeded after 0.1 seconds
note: keeping build directory `/tmp/guix-build-gcl-2.6.12-2.d3335e2.drv-4'
guix build: error: derivation `/gnu/store/kljywjw5a3wpcqk67p1isrrgy5yxgp21-gcl-2.6.12-2.d3335e2.drv' may not be deterministic: output `/gnu/store/5zzfw856c1acrmalsdznm1093mkvnwls-gcl-2.6.12-2.d3335e2' differs from ‘/gnu/store/5zzfw856c1acrmalsdznm1093mkvnwls-gcl-2.6.12-2.d3335e2-check’
diego <at> GLaDOS ~$ /gnu/store/5zzfw856c1acrmalsdznm1093mkvnwls-gcl-2.6.12-2.d3335e2-check/bin/gcl
Speicherzugriffsfehler
diego <at> GLaDOS ~$ guix build gcl -s i686-linux --check --keep-failed

[...]

phase `compress-documentation' succeeded after 0.1 seconds
note: keeping build directory `/tmp/guix-build-gcl-2.6.12-2.d3335e2.drv-3'
guix build: error: derivation `/gnu/store/p7r9c9kqf4gafik0a3q9fl0ry8hks99f-gcl-2.6.12-2.d3335e2.drv' may not be deterministic: output `/gnu/store/cbw0k4apa6qiqfm7g9j0lzfbzfk6mxj2-gcl-2.6.12-2.d3335e2' differs from ‘/gnu/store/cbw0k4apa6qiqfm7g9j0lzfbzfk6mxj2-gcl-2.6.12-2.d3335e2-check’
diego <at> GLaDOS ~$ /gnu/store/cbw0k4apa6qiqfm7g9j0lzfbzfk6mxj2-gcl-2.6.12-2.d3335e2-check/bin/gcl
Speicherzugriffsfehler

--8<---------------cut here---------------end--------------->8---

GCL works fine on armhf (I did not try it on aarch64).

I run Guix System (commit: 571a01d) on x86_64.

Regards,

Diego


[0]: https://berlin.guixsd.org/build/943168 (x86_64)
[1]: https://berlin.guixsd.org/build/943189 (i686)


[Message part 3 (message/rfc822, inline)]
From: Diego Nicola Barbato <dnbarbato <at> posteo.de>
To: 34484-done <at> debbugs.gnu.org
Subject: Re: GCL: segfault on invocation on x86_64 and i686
Date: Fri, 27 Sep 2019 09:00:29 +0200
Hi Guix,

I'm closing this bug since it has been fixed a while ago as a side
effect of … something.  I don't know how it was fixed or even if it was
fixed on purpose, but I'm glad it's gone.

Regards,

Diego


This bug report was last modified 5 years and 321 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.