ASDF bug https://bugs.launchpad.net/asdf/+bug/1502323 reveals some massive instability in the way CLISP handles logical pathnames, plus a reproducible case of unexplained segfault.
If and when you have time to look at it, instructions to reproduce are provided. And in case it matters to reproduce, my clisp build script is in fare-scripts. Ping me if and when you have time to look at the bug.
is this the same as bug#677?
please supply a reproducible test case.
thanks
Last edit: Sam Steingold 2016-08-26
I believe this is a different bug, and possibly not directly related to pathname handling.
I tried to reproduce the bug and couldn't reproduce it using the latest CLISP by following the instructions above. However, when I thought everything was fine, I found what might be the same bug: deterministic SIGSEGV for me (this time in test-program.script), but extremely sensitive to source code modification -- adding a (+ 1 1) at the end of make-hello-world.lisp prevents the SIGSEGV, making it a heisenbug. GRRRRRRR!
I can reliably reproduce on my machine (Linux x64, Ubuntu 16.04.1 LTS) with a clisp compiled from 15631:bf16ec104ed4 with the myclisp script in fare-scripts, using the test suite of ASDF 3.1.7.8:
make t l=clisp t=test-program.script
Please advise.
This bug may be renamed from "Instability in pathname handling" to "Deterministic SIGSEGV heisenbug" or some such.
you can change the name of the bug using the "edit" button.
you can also try compiling with gc-safety checks and seeing if you get an abort instead of the segfault:
./configure --cbc --with-debug CC='g++' build-g-gxx
thanks
I tried adding --with-debug CC='g++' and it failed to compile:
Related
clisp: clisp
Last edit: François-René Rideau 2016-08-29
Also, I seem to be lacking access rights and can't change the bug title.
your compilation succeded! only the benchmarks failed (as expected).
cd build-dir; make base
and usebuild-dir/clisp
as your clispOK so using that clisp, all tests pass (slowly).
But since it's a heisenbug, it could be that disturbing the setup a little could make it reappear. I don't have the courage of running tests on every version of asdf or so to find out where it segfaults. At least not at this point.
I'm seeing segfaults in asdf-pathname-test as of asdf-3.1.7.25 again (didn't see those with 3.1.7.24). Very Heisenbugish indeed. Impossible for me to provide a reliable way of reproducing this. I'm on 15668:01c69ac1e332.
Maybe
make t l=clisp t=asdf-pathname-test.script CLISP=/path/to/clisp
segfaults for you. Maybe it doesn't...