maxima crashed with SIGSEGV

Bug #410597 reported by Andrea
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
maxima (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

Binary package hint: maxima

1)
lsb_release -rd
Description: Ubuntu karmic (development branch)
Release: 9.10

2)
apt-cache policy maxima
maxima:
  Installato: 5.17.1-1ubuntu1
  Candidato: 5.17.1-1ubuntu1
  Tabella versione:
 *** 5.17.1-1ubuntu1 0
        500 http://it.archive.ubuntu.com karmic/universe Packages
        100 /var/lib/dpkg/status

3)
Trying the examples in the main page, the second [diff(cos(x),x)] works well; the first [integrate(1/(1+x^3),x], don't.

4)
Firts time I double click the formula, the program return the following message:
"(%i1) 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."

The second time, an "Error" window appear with the message: "Error sending to Maxima:: can not find channel named "sock7". You may need to Restart".

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Sat Aug 8 08:37:13 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/maxima/5.17.1/binary-gcl/maxima
Package: maxima 5.17.1-1ubuntu1
ProcCmdline: /usr/lib/maxima/5.17.1/binary-gcl/maxima -eval (cl-user::run) -f -- -r :lisp\ (start-server\ 4008)
ProcEnviron:
 SHELL=/bin/bash
 LANG=it_IT.UTF-8
 LANGUAGE=it_IT.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-3.19-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
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: maxima crashed with SIGSEGV
Uname: Linux 2.6.31-3-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Andrea (andrea-correani-deactivatedaccount) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:?? ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
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.

Changed in maxima (Ubuntu):
importance: Undecided → Medium
status: New → Triaged
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.