[Octave-bug-tracker] [bug #48482] Crash after plot interaction

[Lachlan Andrew]

Follow-up Comment #13, bug #48482 (project octave):

I have been thinking of having something in the signal handler that takes a
stack trace and tries to respond accordingly.

Suitable responses could include
1. Report "this looks like bug #xxxxx.  A work-around is XYZ"
2. Print "An internal error has occurred.  Please save your session and then
restart", followed by throwing an exception to be caught in toplev.cc.  This
is what Matlab does.  (Yes, I managed to get Matlab to crash :)

That would add to the maintenance burden, but would greatly reduce the user
impact of crashes due to things outside our control.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?48482>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/