octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #40443] MinGW: Octave crashes on exit


From: Philip Nienhuis
Subject: [Octave-bug-tracker] [bug #40443] MinGW: Octave crashes on exit
Date: Fri, 01 Nov 2013 09:01:50 +0000
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.11) Gecko/20100701 SeaMonkey/2.0.6

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

                 Summary: MinGW: Octave crashes on exit
                 Project: GNU Octave
            Submitted by: philipnienhuis
            Submitted on: Fri 01 Nov 2013 10:01:49 AM CET
                Category: None
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Crash
                  Status: None
             Assigned to: None
         Originator Name: Philip Nienhuis
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: Microsoft Windows

    _______________________________________________________

Details:

Upon exit, MinGW builds (mxe-cross-built) yield the following error message:

octave-cli:2> error: Permission denied
error: ignoring octave_execution_exception while preparing to exit
panic: Segmentation violation -- stopping myself...
attempting to save variables to 'octave-workspace'...
save to 'octave-workspace' complete 


(also reported here:
http://octave.1599824.n4.nabble.com/Problems-with-the-Windows-build-tc4658593.html#a4658641
 )

I now see after restart that the history hasn't updated, so this exit crash
does affect some functionality.

Now I've seen a similar-looking issue before; in that case it had to do with
write permissions on the (location of the) history file. It was a bit sneaky
in the sense that unwary users couldn't know what the actual issue was.

But whatever the underlying issue, Octave shouldn't crash, not even on exit,
but rather catch the issue and somewhat politely suggest the user what to do.


I'll investigate later today (no time now) what the current underlying issue
could be and report back.





    _______________________________________________________

Reply to this item at:

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

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]