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

[Philip Nienhuis]

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

My main point -again!- is that Octave:
1. should give more info on exactly what "permission is denied"
2. shouldn't segfault/crash if octave_hist turns out to be read-only (be it
with or w/o running __run_test_suite__.m)

Otherwise you're right, with yesterday's build (Nov 23rd) I do not see it
anymore on WinXP (and Win7, see below). I'll have to try on Win8 (at work) as
well, that's where I hit this the most (comment #9 referred to Win8), but I'll
be at my own desk next Wednesday at the earliest.

I just saw that on my Win7 box the file:
C:\Users\Philip\.octave_hist
had been set to read-only again. After wiping the read-only flag Octave
behaves "as it should".
I'm puzzled as to which process is doing this - I had reset it to writable a
while ago, even several times.

My builds are usually not much older than 2 days. I doubt whether this
read-only octave_hist has anything to do with mxe itself; I've hit this before
with 3.6.x and 3.2.x MinGW builds.


    _______________________________________________________

Reply to this item at:

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

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