[Octave-bug-tracker] [bug #53838] variable editor displays out of bounds error too frequently

[Dan Sebald]

Follow-up Comment #3, bug #53838 (project octave):

I've tried your examples here.  There are certainly some issues, but I don't
see any type of "out of bound" error.  I'm seeing:

Example 1:  No errors visibly detected.

Example 2:  This one I can repeat.  I've included a screen shot of the end
result (see example_2_screen_1_Screenshot_from_2018-05-07_12-31-06.png).

Out of curiosity, I wondered about the displayed "Variable a.b(2).e not found"
in the Variable Editor, whether that would be the thing that is causing this,
so I deleted that window and the message went away.  See the second attached
screen shot (example_2_screen_2_Screenshot_from_2018-05-07_12-38-32.png).  So,
it is the presence of that discarded variable in the Variable Editor that is
causing this.  But I should note the first time that I had deleted the
variable a.b(2).e in the Variable Editor I saw a bad error message dialog and
debugging quit and Octave returned to the command line.

[
Here's an ancillary observation...  I didn't follow the example properly with
the first attempt.  I created the function testConflict resident, not in a
file.  Octave displays a dialog box about "testConflict does not exist" and
should a file be created?  See the third attached screen shot
(example_2_screen_3_Screenshot_from_2018-05-07_12-47-42.png).  This happens
with each "dbcont" and also the editor is temporarily raised to the front.

So, the question is what should happen in this scenario?  I can say "Yes" and
a blank file is then opened and this dialog box stops appearing with new
"dbcont", but what state is Octave debugger in then since there is this
resident function "testConflict" an empty file "testConflict" (not
testConflict.m, but testConflict)?  It seems to me this behavior is somewhat
arbitrary.
]

Example 3:  Definitely a crash, and it happens at the line


a.b(2).c = 'string';


i.e., when the variable a.b is expanded.  I see an "octave exited with signal
6".  The commands (sans "openvar a") do not crash in the CLI version of
Octave.  But this is not a debug issue.  So I'll create another bug report for
this crash bug.

(file #44114, file #44115, file #44116)
    _______________________________________________________

Additional Item Attachment:

File name: example_2_screen_1_Screenshot_from_2018-05-07_12-31-06.png Size:127
KB
File name: example_2_screen_2_Screenshot_from_2018-05-07_12-38-32.png Size:90
KB
File name: example_2_screen_3_Screenshot_from_2018-05-07_12-47-42.png Size:125
KB


    _______________________________________________________

Reply to this item at:

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

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