[Octave-bug-tracker] [bug #54231] GUI attempts to open file for function declared at top-level

[Dan Sebald]

Follow-up Comment #4, bug #54231 (project octave):

I saw something probably related the other day, but disregarded it because it
didn't seem too significant.  But now that I try this again, the bug seems
worse than I remember (but the crash is intermittent).  This could be a GUI
issue too, and not necessarily something fundamental in the way breakpoints
are processed.  It may be worth addressing the following at the same time:

1) Launch Octave with GUI and open the Editor, either floating or not
floating.

2) Create a new file by selecting the New Script icon (the left-most icon in
the toolbar).

3) Without adding any text to the file titled "<unnamed>", mouse click in the
empty left column where breakpoint icons typically appear.

The result is a dialog box that appears titled "Change Directory or Add
Directory to Load Path" with a message "The file does not exist in the load
path.  To run or debug the function you are editing, you must either change to
the directory or add that directory to the load path."  I'm attaching a screen
shot of the dialog box.

My way of thinking is that I've clicked on a line where for certain there
cannot be a breakpoint.  Perhaps it isn't easy to determine if there can or
can't be a breakpoint because the design may intentionally be to select the
*nearest* breakpoint.

Anyway, if I then select the X to cancel the dialog box, Octave GUI crashes
with "octave exited with signal 11".

If I repeat steps 1 and 2, but this time place a simple for-loop in the new
file *without saving* then again click in the breakpoint column, the error
message is slightly different.  It is titled "Octave Editor" and reads "Cannot
add breakpoint to modified file.  Save and add breakpoint, or cancel?"  This
time canceling does not crash Octave GUI.

Again, my report seems like it could be more GUI related, but the
inconsistency of the error message seems strange and the "The file does not
exist in load path" message is reminiscent of the original post.

(file #44490, file #44491)
    _______________________________________________________

Additional Item Attachment:

File name:
dialog_when_pressing_breakpoint_area_of_empty_new_file_Screenshot_from_2018-07-02_12-14-30.png
Size:37 KB
File name:
dialog_when_pressing_breakpoint_area_of_forloop_unsaved_new_file_Screenshot_from_2018-07-02_12-38-25.png
Size:20 KB


    _______________________________________________________

Reply to this item at:

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

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