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.
(%i3) length("string");
Segmentation fault
ste@localhost:~/build/maxima-5.23.2$
Maxima and Clisp:
(%i4) length("string");
Maxima encountered a Lisp error:
CAR: #1="string" is not a list
Automatically continuing.
To enable the Lisp debugger set *debugger-hook* to nil.
I'm using the latest cvs version of gcl and Maxima 5.23.2, on Slackware
Gnu/Linux 13.1.
Stefano
_______________________________________________
Gcl-devel mailing list
Gcl-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/gcl-devel
