octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Carnë Draug
Subject: [Octave-bug-tracker] [bug #49609] Ctrl+C crashes Octave and the Desktop
Date: Thu, 16 Feb 2017 22:12:07 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0

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

I had a session with jwe on IRC where he tried to find more details about this
bug. Seems that the problem is that Octave sends signals to its whole process
group.  When starting Octave from the launcher, Octave will be in the same
process group has the session manager and so Octave.

jwe on IRC:
> OK.  One difference is that when you do it with Octave, gnome-session is
getting the interrupt signal (= 2) directly instead of getting a terminate
signal (= 15).  But the real question is why would sending SIGINT to Octave
generate an interrupt to the session? I'm guessing it is this code, and the
session is in the same process group? 
http://hg.savannah.gnu.org/hgweb/octave/file/0c9195baea1a/libgui/src/thread-manager.cc#l69
 

Looking at list of processes, I see the following for the Octave started from
the Gnome launcher (I added the "--norc" to the desktop file to make sure the
configuration was not the cause of it):


 PPID   PID  PGID   SID TTY      TPGID STAT   UID   TIME COMMAND
[...]
 4131  4140  4140  4140 ?           -1 Ssl   1000   0:00      \_
x-session-manager
[...]
 4140  4279  4140  4140 ?           -1 Sl    1000   2:47          \_
/usr/bin/gnome-shell
[...]
 4279 18136  4140  4140 ?           -1 Sl    1000   0:01              \_
/usr/local/libexec/octave/4.2.0/exec/x86_64-pc-linux-gnu/octave-gui --norc
--force-gui


While starting octave from the command line and the same options:


 PPID   PID  PGID   SID TTY      TPGID STAT   UID   TIME COMMAND
[...]
18335 18336 18336 18336 ?           -1 Ssl   1000   0:00          \_
/usr/local/libexec/octave/4.2.0/exec/x86_64-pc-linux-gnu/octave-gui --norc
--force-gui


Why setting OMP_NUM_THREADS=1 solves the issue on my system I don't
understand.

    _______________________________________________________

Reply to this item at:

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

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]