[Octave-bug-tracker] [bug #44470] ctrl-c after pause gives crash/segfault

[Dan Sebald]

Follow-up Comment #4, bug #44470 (project octave):

I've noticed a similar thing on linux.  It's difficult to repeat.  I've been
working on a demo that uses inputdlg and similar functions.  I had problems
printing a plot because the figure disappeared before the print command
executed (when it seemed like that shouldn't happen).  So I placed "pause(0)"
in the code to force a drawnow().

It seems that if I hit control-c during the inputdlg display, sometimes Octave
GUI will crash right after returning from the dialog box closing.  Now, those
inputdlg() routines aren't the best programmed.  They were just something to
get started.  (A good comm concept is needed.)  Nonetheless, I thought they
were fairly robust in the past.  So I'm more inclined to think there is a
connection to "pause".

In any case, another strange thing is that if I type "cancel" for the dialog
box, it's as if the lines of code after the inputdlg() don't get run, but when
hitting OK they do.  It's all sort of vague.  But maybe the signal is being
corrupted somehow, e.g., a cancel causes a bogus signal to the core????  Not
much help, I know.

    _______________________________________________________

Reply to this item at:

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

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