[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Conflicting signal handlers of octave and qt
From: |
Torsten |
Subject: |
Conflicting signal handlers of octave and qt |
Date: |
Thu, 13 Feb 2014 21:47:01 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 |
There are several bug reports for the GUI that all seem to be related to
a conflict between the octave and qt signal handler for SIGCHLD
(https://savannah.gnu.org/bugs/?38305, especially comments #36 and #37).
The mentioned issues are fixed by commenting out the line 640 in
sighandlers.cc:
639 #ifdef SIGCHLD
640 octave_set_signal_handler (SIGCHLD, sigchld_handler);
641 #endif
Octave's signal handling is beyond my knowledge. What is the purpose of
the octave SIGCHLD-handler? Is there a chance for omitting the handler
when running the gui?
Torsten
- Conflicting signal handlers of octave and qt,
Torsten <=