Comment #19 on issue 2825 by [email protected]: breakpoint resolved to
incorrect location
http://code.google.com/p/v8/issues/detail?id=2825
This is happening to me in the latest stable release and has been for
months. I'll set a few breakpoints and the Chrome debugger will show itself
having stopped anywhere from a few to several dozen lines past where it
actually is. I'm not using nodejs or any IDEs, just the regular Chrome
Javascript debugger. I've had to go back to using Firebug when debugging
Javascript because my breakpoints in Chrome are basically useless. I have
no idea which one is actually being triggered without manually inspecting
local variables throughout my code.
It also happens when using a "debugger;" statement. I have "disable cache
while DevTools are open" enabled.
I love Chrome but how is this seriously still an issue after several
months? My coworkers are having the same problem.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
