Bug 669172 – dev-lisp/ecl-16.1.3 : ;;; Loading src:lsp;setf.lsp/.../sh:line <snip>: <snip> Segmentation fault ECLDIR= pwd / ./ecl_min compile

• Product: Gentoo Linux
• Status: CONFIRMED ---

[Description Toralf Förster 2018-10-21 07:58:53 UTC]

;;; Loading src:lsp;evalmacros.lsp
;;; Loading src:lsp;cmuutil.lsp
;;; Loading src:lsp;setf.lsp/bin/sh: line 4: 22882 Segmentation fault      ECLDIR=`pwd`/ ./ecl_min compile
make[1]: *** [Makefile:241: bin/ecl] Error 139
make[1]: Leaving directory '/var/tmp/portage/dev-lisp/ecls-16.1.3/work/ecl-16.1.3/build'
make: *** [Makefile:72: all] Error 2

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

  This is an unstable amd64 chroot image at a tinderbox (==build bot)
  name: 17.0-systemd_abi32+64_20181020-092847

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

  Please see the tracker bug for details.

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

Available Python interpreters, in order of preference:
  [1]   python3.6
  [2]   python2.7 (fallback)
Available Ruby profiles:
  [1]   ruby23 (with Rubygems) *



emerge -qpvO dev-lisp/ecls
[ebuild  N    ] dev-lisp/ecls-16.1.3  USE="cxx gengc libatomic threads unicode -X -debug -emacs -precisegc" CPU_FLAGS_X86="sse"

[Comment 1 Toralf Förster 2018-10-21 07:58:56 UTC]

Created attachment 552054 [details]
emerge-info.txt

[Comment 2 Toralf Förster 2018-10-21 07:58:59 UTC]

Created attachment 552056 [details]
dev-lisp:ecls-16.1.3:20181021-070537.log

[Comment 3 Toralf Förster 2018-10-21 07:59:01 UTC]

Created attachment 552058 [details]
emerge-history.txt

[Comment 4 Toralf Förster 2018-10-21 07:59:04 UTC]

Created attachment 552060 [details]
environment

[Comment 5 Toralf Förster 2018-10-21 07:59:07 UTC]

Created attachment 552062 [details]
etc.portage.tbz2

[Comment 6 Toralf Förster 2018-10-21 07:59:10 UTC]

Created attachment 552064 [details]
logs.tbz2

[Comment 7 Toralf Förster 2018-10-21 07:59:13 UTC]

Created attachment 552066 [details]
temp.tbz2

[Comment 8 Andreas K. Hüttel 2018-12-30 20:23:19 UTC]

@common-lisp: any idea what's going on here?

[Comment 9 Andreas K. Hüttel 2018-12-31 10:28:23 UTC]

1) This is more likely a gcc-8 problem than a glibc problem, I suspect.
2) I can't reproduced it anywhere (not on amd64, not on ~amd64)

So let's assume it has been fixed. Somewhere.

[Comment 10 Toralf Förster 2019-04-04 15:22:17 UTC]

it is still an issue at unstable amd64 tinderbox image 17.1-no-multilib_libressl_20190401-161804

[Comment 11 Toralf Förster 2019-04-04 15:22:20 UTC]

Created attachment 571810 [details]
emerge-info.txt

[Comment 12 Toralf Förster 2019-04-04 15:22:23 UTC]

Created attachment 571812 [details]
dev-lisp:ecls-16.1.3:20190404-064804.log

[Comment 13 Toralf Förster 2019-04-04 15:22:26 UTC]

Created attachment 571814 [details]
emerge-history.txt

[Comment 14 Toralf Förster 2019-04-04 15:22:29 UTC]

Created attachment 571816 [details]
environment

[Comment 15 Toralf Förster 2019-04-04 15:22:32 UTC]

Created attachment 571818 [details]
etc.portage.tbz2

[Comment 16 Toralf Förster 2019-04-04 15:22:34 UTC]

Created attachment 571820 [details]
logs.tbz2

[Comment 17 Toralf Förster 2019-04-04 15:22:37 UTC]

Created attachment 571822 [details]
temp.tbz2

[Comment 18 Tom Gillespie 2019-05-27 18:46:26 UTC]

I am encountering this issue on a system using x86_64-pc-linux-gnu-8.2.0, and sys-libs/glibc-2.29-r2. Will attach the relevant files.

[Comment 19 Tom Gillespie 2019-05-27 18:53:08 UTC]

Created attachment 577908 [details]
emerge pqv output

[Comment 20 Tom Gillespie 2019-05-27 18:53:40 UTC]

Created attachment 577910 [details]
emerge --info output

[Comment 21 Tom Gillespie 2019-05-27 18:55:07 UTC]

Created attachment 577912 [details]
emerge build.log

[Comment 22 Tom Gillespie 2019-05-27 18:55:36 UTC]

Created attachment 577914 [details]
emerge environment

[Comment 23 Tom Gillespie 2019-05-27 19:14:11 UTC]

I do not encounter this issue when building from the latest git sources.
https://gitlab.com/embeddable-common-lisp/ecl/ 7fd97549d66f3fdeefa0ce304ce925af2e1e0bd6

[Comment 24 Cyprien Nicolas (fulax) 2019-06-15 14:22:09 UTC]

(In reply to Andreas K. Hüttel from comment #8)
> @common-lisp: any idea what's going on here?

After a few tests, the combination USE="gengc threads" makes the build to fail (USE="-libatomic" fails too). The pkg_setup phase says the gengc and preceisegc flags are both experimental.

[Comment 25 Michael Orlitzky 2022-01-18 20:14:34 UTC]

*** Bug 735656 has been marked as a duplicate of this bug. ***

[Comment 26 Michael Orlitzky 2022-01-18 21:50:05 UTC]

With ecls-21.2.1, the generational and precise garbage collectors are considered stable. ECL now builds with USE="gengc" although the result still crashes while running SageMath's maxima tests. USE=threads is irrelevant.

USE=precisegc works fine.

Suggestion: mask USE=gengc for now, or put back the pkg_setup() warning about it (and direct bug reports upstream).