[Gcl-devel] Segmentation fault with Maxima's "length" and gcl
From:
Stefano Ferri
Subject:
[Gcl-devel] Segmentation fault with Maxima's "length" and gcl
Date:
Wed, 16 Feb 2011 22:30:00 +0100
I was playing with two different Maxima builds, one made against gcl, the other one compiled against clisp. The following command:
length("string");
that must produce an error, if repeated twice, causes gcl to produce a segmentation fault and Maxima to exit. Moreover, the first time takes about 2 seconds to get the error, while with clisp the error message is displayed immediately, and no segfault is produced by further errors.
Maxima and Gcl
(%i2) length("string");
Maxima encountered a Lisp error:
Error in PROGN [or a callee]: Caught fatal error [memory may be damaged]
Automatically continuing.
To enable the Lisp debugger set *debugger-hook* to nil.