abrt version: 1.1.13 architecture: x86_64 Attached file: backtrace cmdline: /usr/lib64/maxima/5.20.1/binary-clisp/lisp.run -q -M /usr/lib64/maxima/5.20.1/binary-clisp/maxima.mem '' -- -r ':lisp (start-client 4008)' '' '' '' '' '' '' '' component: maxima crash_function: elastic_newline_pending_p executable: /usr/lib64/maxima/5.20.1/binary-clisp/lisp.run kernel: 2.6.34.7-56.fc13.x86_64 package: maxima-runtime-clisp-5.20.1-4.fc13 rating: 4 reason: Process /usr/lib64/maxima/5.20.1/binary-clisp/lisp.run was killed by signal 11 (SIGSEGV) release: Fedora release 13 (Goddard) time: 1285959043 uid: 500
Created attachment 451094 [details] File: backtrace
Curious, any particular reason you're using maxima-runtime-clisp over the default maxima-runtime-sbcl ?
*** This bug has been marked as a duplicate of bug 625599 ***