Bug 465375 - maxima-runtime-sbcl segfaults on x86_64
maxima-runtime-sbcl segfaults on x86_64
Status: CLOSED WORKSFORME
Product: Fedora
Classification: Fedora
Component: maxima (Show other bugs)
rawhide
x86_64 Linux
medium Severity medium
: ---
: ---
Assigned To: Rex Dieter
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-10-02 19:07 EDT by petrosyan
Modified: 2008-10-03 09:37 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-10-03 09:37:58 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description petrosyan 2008-10-02 19:07:48 EDT
Description of problem:
maxima-runtime-sbcl segfaults on x86_64

Version-Release number of selected component (if applicable):
maxima-runtime-sbcl-5.16.3-2.fc10.x86_64

How reproducible:
Always

Steps to Reproduce:
run maxima from a terminal
  
Actual results:
$ maxima
fatal error encountered in SBCL pid 10407(tid 1185520):
can't load .core for different runtime, sorry

Welcome to LDB, a low-level debugger for the Lisp runtime environment.
ldb> 


Expected results:
no segfaults

Additional info:
in dmesg i get the following message:

sbcl[9820]: segfault at 0 ip 000000365ea725c0 sp 00007fff66d36488 error 4 in libc-2.8.90.so[365ea00000+16c000]
Comment 1 Rex Dieter 2008-10-03 09:37:58 EDT
Please upgrade, and reopen/comment if it doesn't fix the issue.

$ rpm -q sbcl maxima-runtime-sbcl
sbcl-1.0.21-1.fc10.x86_64
maxima-runtime-sbcl-5.16.3-3.fc10.x86_64

$ maxima
Maxima 5.16.3 http://maxima.sourceforge.net
Using Lisp SBCL 1.0.21
Distributed under the GNU Public License. See the file COPYING.
Dedicated to the memory of William Schelter.
The function bug_report() provides bug reporting information.
(%i1) 1+1;
(%o1)                                  2

Note You need to log in before you can comment on or make changes to this bug.