clisp crashed in impish compiling xindy
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
clisp (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
xindy (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
clisp segfaults wehn compiling xindy in impish
for i in src tex2xindy user-commands; do /usr/bin/make -C $i all || exit 1; done
make[1]: Entering directory '/<<PKGBUILDDIR
sed 's|@MODULEDIR[
/usr/bin/clisp -q -E iso-8859-1 -c base.lsp -o base.fas
;; Compiling file /<<PKGBUILDDIR>
;; Wrote file /<<PKGBUILDDIR>
0 errors, 0 warnings
/usr/bin/clisp -q -E iso-8859-1 -c ordrules.lsp -o ordrules.fas
;; Compiling file /<<PKGBUILDDIR>
*** - handle_fault error2 ! address = 0x45b926e6958 not in [0x50000020000,
SIGSEGV cannot be cured. Fault address = 0x45b926e6958.
GC count: 4
Space collected by GC: 3451320
Run time: 0 84663
Real time: 0 472415
GC time: 0 18809
Permanently allocated: 165256 bytes.
Currently in use: 4447024 bytes.
Free space: 52452 bytes.
make[1]: *** [Makefile:507: ordrules.fas] Segmentation fault (core dumped)
Chances are this is related to another case which is clisp no-change-rebuild being FTFBS on ppc64/s390x which ?by accident? are exactly the platform this crashes.
Maybe a library transitioned as there was no test hitting this, but now that all is in impish this indirectly breaks the xindy builds - just a theory for now.
tags: | added: update-excuse |
Attaching a full backtrace of the fail.