build_info, (This is from the ubuntu package)
Maxima version: 5.13.0
Maxima build date: 3:56 12/15/2007
host type: x86_64-unknown-linux-gnu
lisp-implementation-type: GNU Common Lisp (GCL)
lisp-implementation-version: GCL 2.6.8
Here's how:
$ yes "integrate(1/(-1 + x^n), x);" | maxima
Maxima 5.13.0 http://maxima.sourceforge.net
Using Lisp GNU Common Lisp (GCL) GCL 2.6.8 (aka GCL)
Distributed under the GNU Public License. See the file COPYING.
Dedicated to the memory of William Schelter.
This is a development version of Maxima. The function bug_report()
provides bug reporting information.
(%i1) /
[ 1
(%o1) I ------ dx
] n
/ x - 1
(%i2) /
[ 1
(%o2) I ------ dx
] n
/ x - 1
(%i3) /
[ 1
(%o3) I ------ dx
] n
/ x - 1
(%i4) 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.
(%i5) /
[ 1
(%o5) I ------ dx
] n
/ x - 1
(%i6) Segmentation fault
Not observed with Maxima 5.16post + GCL 2.6.7 or 5.9.0 + GCL 2.5.0 (both on Fedora Linux).
I'm guessing that this is a problem with GCL 2.6.8 in general or its x86_64 port in particular. I don't think any of the regular developers have access to an x86_64 system to debug this. I'm marking this item "works for me" and marking it "pending" which means it will stay open for 2 weeks before being closed automatically.
Probably the best course of action at this point is for the person who originated this bug report to forward it (with these comments) to the package maintainer who created the Ubuntu package in question.
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).