octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #59677] Debug pointer doesn't move with debug


From: Philip Nienhuis
Subject: [Octave-bug-tracker] [bug #59677] Debug pointer doesn't move with debug steps during 'nested' debugging
Date: Sun, 13 Dec 2020 17:33:07 -0500 (EST)
User-agent: Mozilla/5.0 (Windows NT 6.1; rv:52.0) Gecko/20100101 Firefox/52.0

URL:
  <https://savannah.gnu.org/bugs/?59677>

                 Summary: Debug pointer doesn't move with debug steps during
'nested' debugging 
                 Project: GNU Octave
            Submitted by: philipnienhuis
            Submitted on: Sun 13 Dec 2020 11:33:05 PM CET
                Category: GUI
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Incorrect Result
                  Status: None
             Assigned to: None
         Originator Name: Philip Nienhuis
        Originator Email: 
             Open/Closed: Open
                 Release: 6.1.0
         Discussion Lock: Any
        Operating System: Microsoft Windows

    _______________________________________________________

Details:

First off, I don't know if this is a real bug; but what I see is surely
counter-intuitively.
Steps to reproduce, all in the GUI:

Define two functions funca and funcb, more or less as follows:

function a = funca ()
  a = 1;
  a = 2;
  a = funcb ();
  a = 4;
endfunction



function b = funcb ()
  b = 1;
  b = 2;
  b = 3;
  b = 4;
endfunction


In both functions, add a breakpoints at L.2.

Then, type 'funca'
=> execution stops in funca at L2, fine.

Now, in funca.m select L.4 'a = funcb ();' and press F9
=> executions stops in funcb at L2, and the prompt changes to '[1]debug>',
fine.

Then, press the "Step" button repeatedly.
The 'debug pointer' (yellow arrow) stays at L.2 (that is the bug) but in the
Workspace pane the value of 'b' is increased until funcb is finished (which
AFAIU is correct).
So the debug pointer doesn't follow the "active" line in funcb. IOW, a sort of
"blind" debugging stepping.

Going on clicking the 'Step' button, execution is picked up again in funca and
the debug pointer correctly follows the "active" lines, also in funcb.
I do have the "Always show debug breakpoints and pointers (opens related file
if closed)" set.





    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?59677>

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]