Bug 668586 – dev-lisp/clisp-2.49.92 : make: *** [Makefile:<snip>: compiler.fas]<snip> Segmentation fault

• Status: CONFIRMED
• Product: Gentoo Linux

[Description Toralf Förster 2018-10-14 11:28:27 UTC]

mv lispimag.mem interpreted.mem
./lisp.run -B . -N locale -E UTF-8 -Emisc 1:1 -Epathname 1:1 -norc -m 2MW -M interpreted.mem -q -c ../src/compiler.lisp -o ./
make: *** [Makefile:1547: compiler.fas] Segmentation fault
 * ERROR: dev-lisp/clisp-2.49.92::gentoo failed (compile phase):
 *   emake failed
 * 

  -------------------------------------------------------------------

  This is an unstable amd64 chroot image at a tinderbox (==build bot)
  name: 17.0_libressl_20181006-211214

  -------------------------------------------------------------------

gcc-config -l:
 [1] x86_64-pc-linux-gnu-7.3.1
 [2] x86_64-pc-linux-gnu-8.2.0 *

Available Python interpreters, in order of preference:
  [1]   python3.7
  [2]   python3.6
  [3]   python2.7 (fallback)
  [4]   pypy (fallback)
Available Ruby profiles:
  [1]   ruby23 (with Rubygems)
  [2]   ruby25 (with Rubygems) *
java-config:
The following VMs are available for generation-2:


emerge -qpvO dev-lisp/clisp
[ebuild  N    ] dev-lisp/clisp-2.49.92  USE="berkdb gdbm pcre readline unicode zlib -X -dbus -fastcgi -gtk -hyperspec -postgres (-svm) -threads"

[Comment 1 Toralf Förster 2018-10-14 11:28:30 UTC]

Created attachment 551106 [details]
emerge-info.txt

[Comment 2 Toralf Förster 2018-10-14 11:28:32 UTC]

Created attachment 551108 [details]
dev-lisp:clisp-2.49.92:20181013-072147.log

[Comment 3 Toralf Förster 2018-10-14 11:28:35 UTC]

Created attachment 551110 [details]
emerge-history.txt

[Comment 4 Toralf Förster 2018-10-14 11:28:38 UTC]

Created attachment 551112 [details]
environment

[Comment 5 Toralf Förster 2018-10-14 11:28:40 UTC]

Created attachment 551114 [details]
etc.portage.tbz2

[Comment 6 Toralf Förster 2018-10-14 11:28:43 UTC]

Created attachment 551116 [details]
logs.tbz2

[Comment 7 Cyprien Nicolas (fulax) 2019-06-15 12:14:59 UTC]

Thanks for the report. I am unable to reproduce the issue. Could your system might be under memory stress?

Running by hand the failing command seems not to raise any error.

Are you still be able to reproduce the issue? If yes, can you go to the build directory

  /var/tmp/portage/dev-lisp/clisp-2.49.92/work/clisp-2.49.92/builddir

and run the command that failed:

  ./lisp.run -B . -N locale -E UTF-8 -Emisc 1:1 -Epathname 1:1 -norc -m 2MW -M interpreted.mem -q -c ../src/compiler.lisp -o ./


Thanks.

[Comment 8 Toralf Förster 2019-06-15 13:58:39 UTC]

(In reply to Cyprien Nicolas (fulax) from comment #7)
> Thanks for the report. I am unable to reproduce the issue. Could your system
> might be under memory stress?
> 
The tinderbox has 128 GB RAM, 4 TB disk space, but I do limit the mem to 2^30 bytes FWIW:


https://github.com/toralf/tinderbox/blob/master/bin/chr.sh#L74

[Comment 9 Toralf Förster 2019-06-15 19:06:18 UTC]

OTOH can't be reprduced at current images, I'll close this for now

[Comment 10 Toralf Förster 2021-04-17 15:27:08 UTC]

appeared recently at the tinderbox image 17.1-20210411-185226

[Comment 11 Toralf Förster 2021-04-17 15:27:10 UTC]

Created attachment 700395 [details]
emerge-info.txt

[Comment 12 Toralf Förster 2021-04-17 15:27:11 UTC]

Created attachment 700398 [details]
dev-lisp:clisp-2.49.92:20210417-145944.log

[Comment 13 Toralf Förster 2021-04-17 15:27:13 UTC]

Created attachment 700401 [details]
emerge-history.txt

[Comment 14 Toralf Förster 2021-04-17 15:27:15 UTC]

Created attachment 700404 [details]
environment

[Comment 15 Toralf Förster 2021-04-17 15:27:16 UTC]

Created attachment 700407 [details]
etc.portage.tar.bz2

[Comment 16 Toralf Förster 2021-04-17 15:27:17 UTC]

Created attachment 700410 [details]
logs.tar.bz2