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

[Lars Kindermann]

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

Got the mesage. So for Linux (Xubuntu 16.04) I can reliably reproduce the
following behaviour:

Starting Octave 4.0.0 from a terminal and holding down CTRL-C for few
seconds:

address@hidden:~$ octave
octave exited with signal 6
address@hidden:~$ 

Starting Octave 4.3.0 (todays dev) from a terminal and holding down CTRL-C for
*many* seconds:

address@hidden:~$ usr/octave/run-octave
octave exited with signal 2
address@hidden:~$ ^C
address@hidden:~$ usr/octave/run-octave
octave exited with signal 6
address@hidden:~$ 

More often it dies with signal 6. Apport was never triggered yet, so I cannot
provide a stack trace for the current dev. Is there a way to force this?


If I start octave 4.0.0 from a XFCE starter it dies silently after a few
CTRL-C

If I create a XFCE starter for 4.3.0 (current dev) with the command
"usr/octave/run-octave --force-gui" 
and tick the "run in terminal" option it also dies silently after few hundered
CTRL-C, together with this terminal, too.

But when I untick the "run in terminal" option, the very first CTRL-C kills
the whole desktop and leaves me at the login screen. Sometimes, but very
rarely, the process
 
/home/kinder/usr/octave/src/.libs/lt-octave-gui

will survive this.

To me it looks like if the mother process of octave in some cases after a
CTRL-C receives the signal 6 (SIGABRT) and gets killed: If octave is started
by the Desktop it kills the Desktop, if a terminal sits in between, just that
terminal is killed. And when started from command line, the shell seems to
correctly handle and report that signal.

Any idea how I can continue to help digging out the rabbit?


(file #39250)
    _______________________________________________________

Additional Item Attachment:

File name:
usr_lib_x86_64-linux-gnu_octave_4.0.0_exec_x86_64-pc-linux-gnu_octave-gui.1000.crash
Size:149 KB


    _______________________________________________________

Reply to this item at:

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

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