maxima crashed with SIGSEGV
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
Universal error handler called recursively (:ERROR NIL
Maxima encountered a Lisp error:
Error in CONDITIONS:
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/
NonfreeKernelMo
Package: maxima 5.17.1-1ubuntu1
ProcCmdline: /usr/lib/
ProcEnviron:
LANG=en_AU.UTF-8
SHELL=/bin/bash
ProcVersionSign
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
StacktraceTop:?? ()