[Octave-bug-tracker] [bug #49609] Ctrl+C crashes Octave and the Desktop

[Mike Miller]

Follow-up Comment #24, bug #49609 (project octave):

So the Ctrl+C does interrupt the while loop? And at the same time it kills or
forces Unity to restart, but leaves Octave running? That's impressive.

When you say this occurs only once, are you still testing in the same instance
of Octave that was running from the first Unity session? What if you exit
Octave normally and start another one from the Unity panel launcher? Does it
then repeat the process?

If Octave isn't actually crashing itself, only somehow sending a message or a
signal to the parent desktop environment causing it to exit or restart, I
don't have an easy answer how to debug that. Maybe look at the desktop session
logs and see if there are any suggestive messages (I don't know where those
log files would be, maybe ~/.xsession-errors).

    _______________________________________________________

Reply to this item at:

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

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