[Octave-bug-tracker] [bug #40443] MinGW: Octave crashes on exit when octave history file is read-only

[Philip Nienhuis]

Follow-up Comment #16, bug #40443 (project octave):

You probably already have this in the picture; but ever since Rik's comment #8
I have the feeling that the segfault may be largely unrelated to the
non-writable history file.

It turns out the crash occurs irrespective of the read-only status of the
history file (the observation in comment #4 in hindsight does not invalidate
this assumption.) Just running __run_test_suite__ suffices to provoke the
crash on closing Octave on my WinXP box.

So, the whole read-only octave_hist issue seems to be a red herring as far as
the crash/segfault is concerned (although the uninformative error message was
real).

My strategy would be to break up the tests in __run_test_suite__ in sections
and then by narrowing down try to find out which test / tested function sets
the stage for the crash. Do you think this would be a good strategy?
(FYI I've already ignored & removed the jit.tst file in my tests for this bug,
as the jit tests are known to crash MinGW Octave w/o invoking Ctrl-d - bug
#40608.)
Anyway I won't have time for that until next weekend.


As to the fixes:
Of course your changeset works, but in the GUI the message just flashes by for
.1 second before Octave disappears from sight. 
Could there be some timer, of "Press <return>" statement, so that one has a
chance to read the error message before Octave finally closes?


    _______________________________________________________

Reply to this item at:

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

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