You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When reaching the first breakpoint, remove the second:
•| ; # ← debugger is here|print("Hello World");
Continue execution
Example 2
•|print("Hello");
|print("World");
•|print("!");
Set breakpoints where the dots are
Execute the code
When reaching the first breakpoint, step forward until the debugger has reached the third line:
•|print("Hello");
|print("World");
•|print("!"); # ← debugger is here
Remove the second breakpoint:
•|print("Hello");
|print("World");
|print("!"); # ← debugger is here
Continue execution
Cause
When reaching the first breakpoint in the first example or when stepping onto the third line in the second example, the interpreter halts execution just before completing the second breakpoint step, because the breakpoint's sim function returns true. When continuing execution, next_step asserts that the breakpoint's step function returns true. This is however not the case if the breakpoint was deactivated before.
This bug seems to have the preference to occur in front of large audiences 😉.
The text was updated successfully, but these errors were encountered:
When removing an breakpoint while in stepping mode, the following error can occur:
To reproduce:
Example 1
Example 2
Cause
When reaching the first breakpoint in the first example or when stepping onto the third line in the second example, the interpreter halts execution just before completing the second breakpoint step, because the breakpoint's
sim
function returnstrue
. When continuing execution,next_step
asserts that the breakpoint'sstep
function returnstrue
. This is however not the case if the breakpoint was deactivated before.This bug seems to have the preference to occur in front of large audiences 😉.
The text was updated successfully, but these errors were encountered: