[Octave-bug-tracker] [bug #47796] GUI allows breakpoints to be set on empty line at EOF

[Rik]

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

                 Summary: GUI allows breakpoints to be set on empty line at
EOF
                 Project: GNU Octave
            Submitted by: rik5
            Submitted on: Wed 27 Apr 2016 09:26:20 PM PDT
                Category: GUI
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Incorrect Result
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: GNU/Linux

    _______________________________________________________

Details:

Steps to reproduce.

Create a file tmp.m with the following contents


a = 1;
b = 2;
c = 3;
d = 4;




Open tmp.m in the editor.  Double-click to set a breakpoint at line 5 (empty,
but not last line in file).  The breakpoint is set at the last line in the
file (line 6).

To be fair, this might just be dbstop's fault.  When you call it with a line
number it searches for the next breakable line, which might not be the correct
one.


dbstop tmp 5
ans =  7


More fun can be had by entering the editor and using the backspace to delete
empty lines.  The red breakpoint bubble follows the deleted line so it shows
that there is a breakpoint at line 4.  However, if you go back to the command
window and execute dbstatus, the breakpoint is still reported on line 7.





    _______________________________________________________

Reply to this item at:

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

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