Reputation: 51064
I keep finding a scenario where my code stops on a breakpoint in Chrome's debugger, then when I use another tab like "Console", and go back to "Sources", I have lost the place where the code stopped, and I have to click singles-step to get "back on track", but this skips past the sought after breakpoint. Is there some way to get to where the debugger has stopped?
Upvotes: 15
Views: 2221
Reputation: 326
You can use the call stack portion to go to the current location the debugger is stopped at by clicking the top item in the call stack.
As the original writer couldn't submit an image due to his low reputation and the ongoing rules of the site, i will glady provide one for all of us!
Upvotes: 18
Reputation: 114
You can see a line number below. (eg:Line 152, Column 1). So give Ctrl+G+line number. eg: Ctrl+G+152. You can see the breakpoint.
Upvotes: 1
Reputation: 4934
You can click on the breakpoint in the list of breakpoints in the breakpoint panel in Sources and it will take you back there.
Upvotes: 2