Bug 639442

Summary: [abrt] maxima-runtime-clisp-5.20.1-4.fc13: elastic_newline_pending_p: Process /usr/lib64/maxima/5.20.1/binary-clisp/lisp.run was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Rafeek Mikhael <rafeek.mikhael>
Component: maximaAssignee: Rex Dieter <rdieter>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: jamatos, rdieter
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:de77a6e96f92cefb26d40c1c9be5f6e8ad82632e
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-10-12 13:38:46 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Rafeek Mikhael 2010-10-01 18:52:04 UTC 
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
Comment 1 Rafeek Mikhael 2010-10-01 18:52:10 UTC 
Created attachment 451094 [details]
File: backtrace
Comment 2 Rex Dieter 2010-10-01 19:52:18 UTC 
Curious, any particular reason you're using 
maxima-runtime-clisp
over the default
maxima-runtime-sbcl 
?
Comment 3 Rex Dieter 2010-10-12 13:38:46 UTC 

*** This bug has been marked as a duplicate of bug 625599 ***