bugGNU Octave - Bugs: bug #55730, Fault handling by Octave GUI

 
 

bug #55730: Fault handling by Octave GUI

Submitter:  None
Submitted:  Sun 17 Feb 2019 11:39:24 AM UTC
   
 
Category:  GUI Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Feature Request
Status:  Invalid / Not an Octave Bug Assigned to:  None
Originator Name:  DIV Originator Email:  -email is unavailable-
Open/Closed:  * Closed Release:  * other
Operating System:  * Other Fixed Release:  None
Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Mon 18 Feb 2019 08:40:51 PM UTC, comment #1: 

Thank you for your bug report. However, reports that are about a list of general suggestions are not very actionable. Can you help turn this report into something useful?

There are some ways to track what Octave is doing, for example the 'diary' function and the 'octave-workspace' file that is created when Octave crashes. You can ask for help about these on the help mailing list, or file bug reports if you have specific problems with either of those.

Is there a specific bug or feature you would like to focus this bug report on? Please feel free to file as many distinct bug reports as you want for specific issues.

Mike Miller <mtmiller>
Group Member
Sun 17 Feb 2019 11:39:24 AM UTC, original submission:  

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

Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

Only group members can vote.

 

Follow 3 latest changes.

Date Changed by Updated Field Previous Value => Replaced by
2019-04-13 mtmiller StatusNeed Info Invalid / Not an Octave Bug
    Open/ClosedOpen Closed
2019-02-18 mtmiller StatusNone Need Info

Back to the top

Powered by Savane 3.13-3230.
Corresponding source code