Maxima version: 5.17.1
Maxima build date: 14:9 7/13/2009
host type: i686-pc-linux-gnu
lisp-implementation-type: GNU Common Lisp (GCL)
lisp-implementation-version: GCL 2.6.7
On Ubuntu 9.10 when trying to integrate I get the following:
(%i1) integrate(1/(x^3+1),x);
Universal error handler called recursively (:ERROR NIL
CONDITIONS::CLCS-UNIVERSAL-ERROR-HANDLER
""
"Couldn't protect")
Universal error handler called recursively (:ERROR NIL
CONDITIONS::CLCS-UNIVERSAL-ERROR-HANDLER
"" "Couldn't protect")
Maxima encountered a Lisp error:
Error in CONDITIONS::CLCS-UNIVERSAL-ERROR-HANDLER [or a callee]: Caught fatal error [memory may be damaged]
Automatically continuing.
To reenable the Lisp debugger set *debugger-hook* to nil.
It is strange, since on the previous version such error was not present. I am sure it is related to GCL, since with the same version on newly compiled FreeBSD maxima things goe the way they should:
(%i1) integrate(1/(x^3+1),x);
2 x - 1
2 atan(-------)
log(x - x + 1) sqrt(3) log(x + 1)
(%o1) - --------------- + ------------- + ----------
6 sqrt(3) 3
html garbles the text!
(%i2) build_info();
Maxima version: 5.17.1
Maxima build date: 15:58 11/4/2009
host type: i386-portbld-freebsd7.0
lisp-implementation-type: CLISP
lisp-implementation-version: 2.47 (2008-10-23) (built 3466356167) (memory 3466357114)
The difference is in the LISP!
I think this bug report is a duplicate of the bug report ID: 2896728 "function sqrt() crashes". I suppose that again a debian package of Maxima is the source of the problems.
An installation from souce code or cvs with serveral Lisp compilers does not give any problems.
Setting the status to pending and the resolution to duplicate.
Dieter Kaiser
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).