[Octave-bug-tracker] [bug #38305] file dialog causes crash

[Dan Sebald]

Follow-up Comment #27, bug #38305 (project octave):

Hunting around a bit in the code, I think the following might be getting close
to the source.

For a recap, we've found that KDE-linux version of the GUI has standard Qt
file-dialogs that freeze under the condition that there is a Samba server in
the system.  We have a vague notion that the Samba server and QProcess aren't
working together well and somehow the signal about a completed system process
is being masked or blocked in some way from reaching back to the QProcess. 
Furthermore, the before/after line of non-freeze/freeze appears to be line 935
in main-window.cc:

"_octave_qt_link->execute_interpreter ();"

The lines of code beginning the new thread are:


  setlocale (LC_NUMERIC, "C");
  octave_initialize_interpreter (octave_cmdline_argc, octave_cmdline_argv,
                                 octave_embedded);
  octave_execute_interpreter ();


Following the routine "octave_initialize_interpreter" leads to some
modifications to signal handling in a file called siglist.c.  If there is
someone who understands this, please comment.  The line in particular I'm
wondering about is:


# ifdef SIGAIO
      sys_siglist[SIGAIO] = "LAN I/O interrupt";
# endif
-verabtim-

because it seems to me that one might have something to do with with a Samba
server.  Why is Octave modifying (or not modifying but at least monitoring,
I'm not sure) the signals?

This is still a bit fuzzy for me because this is being done in a separate
thread from where the GUI Qt file-dialog is freezing.  But maybe these
low-level modifications affect all threads.


    _______________________________________________________

Reply to this item at:

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

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