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

[Mike Miller]

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

If I had to debug why unity is crashing, I would probably take a look at
https://wiki.ubuntu.com/Unity/FilingBugs. This page suggests a few alternative
ways to debug why unity is crashing, including crash logs being saved in
/var/crash and also how to start unity with gdb from a virtual console.

Doing this _might_ lead to a hint as to why the desktop is
crashing/aborting/exiting because of something Octave is doing, and maybe
indicate that Octave is doing something wrong, or maybe it's something in Qt
or the desktop integration libraries.

This looks like it's rapidly starting to go down a rabbit hole unfortunately,
and I'm still unable to reproduce (not having any machines on hand with either
Unity or KDE).

    _______________________________________________________

Reply to this item at:

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

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