more information about the maxima.el startup problem
Subject: more information about the maxima.el startup problem
From: wang yin
Date: Sun, 18 May 2003 14:33:07 +0800
Hi, I found a *maxima* buffer after M-x maxima
It seems that the maxima process is crashed.
I hope this gives a clue to solve the problem.
Thanks.
GCL (GNU Common Lisp) Version(2.5.0) Thu Dec 5 08:07:35
EST 2002
Licensed under GNU Library General Public License
Contains Enhancements by W. Schelter
Maxima 5.9.0 http://maxima.sourceforge.net
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.
(C1)
Error: Caught fatal error [memory may be damaged]
Fast links are on: do (si::use-fast-links nil) for debugging
Error signalled by CATCH.
Broken at MACSYMA-TOP-LEVEL. Type :H for Help.
MAXIMA>>
Error: Caught fatal error [memory may be damaged]
Fast links are on: do (si::use-fast-links nil) for debugging
Error signalled by MACSYMA-TOP-LEVEL.
Backtrace: SYSTEM:UNIVERSAL-ERROR-HANDLER
Broken at MACSYMA-TOP-LEVEL.
MAXIMA>>
Unrecoverable error: Segmentation violation..
/usr/libexec/maxima/5.9.0/maxima-run-lisp: line 391: 20838
Aborted (core dumped) "$1" $extra_args
$load_arg -eval '(run)'
Process maxima exited abnormally with code 134
--
Wang Yin
DA Lab, Tsinghua University,
100084
Beijing China