[Octave-bug-tracker] [bug #55730] Fault handling by Octave GUI

[anonymous]

URL:
  <https://savannah.gnu.org/bugs/?55730>

                 Summary: Fault handling by Octave GUI
                 Project: GNU Octave
            Submitted by: None
            Submitted on: Sun 17 Feb 2019 11:39:24 AM UTC
                Category: GUI
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Feature Request
                  Status: None
             Assigned to: None
         Originator Name: DIV
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: other
        Operating System: Other

    _______________________________________________________

Details:

In the process of using Octave to 'port' some old MATLAB code (about 1000
lines), I must have crashed Octave around a dozen times.  Although I tried to
isolate the cause of the crash(es), such as by inserting breakpoints, it
proved very difficult.  One reason for that is that I could not tell how far
through the script execution had proceeded before the crash occurred.   

Besides building Octave GUI to be 'fault tolerant', so that it won't crash,
here are some other practical suggestions:

(1)  Create a runtime/launch option to run Octave GUI in a special mode in
anticipation of 'some sort of trouble', which would, say, log all input
commands and console output to log files on disk.  

(2)  Ordinarily keep track of an Octave GUI shutdown/completion/exit code,
which would flag a crash.  Upon the next running of Octave GUI present a
message alerting the user that the application had crashed on the previous
running, and offering options/advice on how to deal with it.  

(3)  Save some of dump file in the event of a crash?  Dump files are generally
pretty useless, I find, but perhaps could be used as supporting information to
attach to bug reports.  

—DIV




    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?55730>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/