maxima "Couldn't protect"

Bug #285420 reported by bp
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
maxima (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: maxima

wxMaxima and Maxima apparently crashes after a quasirandom number of commands. Ctrl-C'ing Maxima during one of those situations raises the SIGSEGV and the crash dump I'm attaching to the bug report.

Here follows a different session, where I try sending the same command two times. The first execution is flawless, the second for some reason fails horribly.

/*
wxMaxima 0.7.1 http://wxmaxima.sourceforge.net
Maxima 5.13.0 http://maxima.sourceforge.net
Copy paste from a wxMaxima session:

Using Lisp GNU Common Lisp (GCL) GCL 2.6.8 (aka GCL)
Distributed under the GNU Public License. See the file COPYING.
Dedicated to the memory of William Schelter.
This is a development version of Maxima. The function bug_report()
provides bug reporting information.
(%i1) wxplot3d(x*y, [x,-5,5], [y,-5,5]);
Output file "/home/badp/maxout.png".
(%o1) << Graphics >>
(%i2) wxplot3d(x*y, [x,-5,5], [y,-5,5]);
Maxima encountered a Lisp error:
 Error in CONDITIONS:HANDLER-CASE [or a callee]: Couldn't protect
Automatically continuing.
To reenable the Lisp debugger set *debugger-hook* to nil.
Maxima encountered a Lisp error:
 Error in PROGN [or a callee]: Couldn't protect
Automatically continuing.
(The above three lines repeated for 41 screenfuls)

This happens quasi-randomly on every session of wxMaxima or maxima itself I try to run. It happens more rarely when I try algebra or matrixes and more quickly when I try plotting, but before or later it will happen.

This bug is not a duplicate of Bug #261056 as execution continues without an OOM error. I also have the problem detailed in bug #261056.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/lib/maxima/5.13.0/binary-gcl/maxima
Package: maxima 5.13.0-3ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: /usr/lib/maxima/5.13.0/binary-gcl/maxima -eval (cl-user::run) -f --
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/lib/surfraw:/home/username/sh
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: maxima
Stacktrace: #0 0x08115695 in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:
 .
 Thread 1 (process 13079):
 #0 0x08115695 in ?? ()
Title: maxima crashed with SIGSEGV
Uname: Linux 2.6.27-7-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin netdev plugdev powerdev sambashare scanner tape video

Revision history for this message
bp (badpazzword) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Iulian Udrea (iulian) wrote :

Could you please confirm if this is the same bug as the bug reported in Debian?

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=480308

Changed in maxima:
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Andres Mujica (andres.mujica) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in maxima:
status: Incomplete → Invalid
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.