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
After stepping through the entirety of one's code, navigate to the line containing the above breakpoint and attempt to remove it using Ctrl+Shift+R -> Toggle Breakpoint
The console window (in debug mode) shows “Removing breakpoint in …”
Yet subsequently, if pressing F5 to refresh the page in Chrome, execution will continue to pause at the breakpoint as if it had not actually been removed
Trying to toggle a breakpoint at the same line of code once again (as if to turn it on again as far as SWI is concerned), the console in debug mode shows “Error from debuggee: Breakpoint at specified location already exists”
I’m using Windows 10, Chrome 7.0.2987.133 (64-bit, the latest non-Canary), ST3 build 3126, SWI releases 1.7.4 and 1.7.5 (all issues appear to occur in both)
The text was updated successfully, but these errors were encountered:
neilalex
changed the title
Breakpoints cannot be removed after starting debugging
Breakpoints will not remove after debugging has begun
Jun 12, 2017
Steps to reproduce
Follow the steps in Saved breakpoints are inoperative and must be re-created #122 to create at least one breakpoint and begin debugging
After stepping through the entirety of one's code, navigate to the line containing the above breakpoint and attempt to remove it using Ctrl+Shift+R -> Toggle Breakpoint
The console window (in debug mode) shows “Removing breakpoint in …”
Yet subsequently, if pressing F5 to refresh the page in Chrome, execution will continue to pause at the breakpoint as if it had not actually been removed
Trying to toggle a breakpoint at the same line of code once again (as if to turn it on again as far as SWI is concerned), the console in debug mode shows “Error from debuggee: Breakpoint at specified location already exists”
I’m using Windows 10, Chrome 7.0.2987.133 (64-bit, the latest non-Canary), ST3 build 3126, SWI releases 1.7.4 and 1.7.5 (all issues appear to occur in both)
The text was updated successfully, but these errors were encountered: