[Octave-bug-tracker] [bug #47190] Trying to evaluate value of a variable on a breakpoint leads to continuation of execution

[Ruslan]

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

                 Summary: Trying to evaluate value of a variable on a
breakpoint leads to continuation of execution
                 Project: GNU Octave
            Submitted by: l0110111
            Submitted on: Thu 18 Feb 2016 02:30:46 PM GMT
                Category: Interpreter
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Other
                  Status: None
             Assigned to: None
         Originator Name: Ruslan
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 4.0.0
        Operating System: GNU/Linux

    _______________________________________________________

Details:

See the following code:

% start code
function octave_test1()
x=5;
y=6;
z=x*y;
w=z+x;
end
% end code

If you add breakpoint at `y=6;` line, then run (press F5), and on hitting the
breakpoint try to evaluate x in the command window (typing x and pressing
Enter), the program will continue and finish.
If you now add a second breakpoint at the next line, the same sequence of
actions leads to hitting the second breakpoint, where you can retype x and
finally get the value.

The expected result is that you don't have to set multiple breakpoints just to
catch the program which ran away from the first breakpoint — it shouldn't
run away on evaluation of a variable.




    _______________________________________________________

Reply to this item at:

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

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