maxima crashed with SIGSEGV

Bug #456987 reported by NickSt
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
maxima (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: maxima

on use of (but not only) gfactor(x^2+1) I get the following

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.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Wed Oct 21 17:47:58 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/maxima/5.17.1/binary-gcl/maxima
NonfreeKernelModules: wl
Package: maxima 5.17.1-1ubuntu1
ProcCmdline: /usr/lib/maxima/5.17.1/binary-gcl/maxima -eval (cl-user::run) -f -- -r :lisp\ (setup-server\ 4010)
ProcEnviron:
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x80e35c7: mov %dl,(%eax)
 PC (0x080e35c7) ok
 source "%dl" ok
 destination "(%eax)" (0x09b44000) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: maxima
Stacktrace:
 #0 0x080e35c7 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x5
StacktraceTop: ?? ()
Tags: ubuntu-unr
ThreadStacktrace:
 .
 Thread 1 (Thread 8874):
 #0 0x080e35c7 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x5
Title: maxima crashed with SIGSEGV
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
NickSt (nick-stavrou) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:?? ()

tags: added: apport-failed-retrace
tags: removed: need-i386-retrace
Revision history for this message
MarcRandolph (mrand) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

visibility: private → public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.