Comment #21 on issue 2825 by [email protected]: breakpoint resolved to
incorrect location
http://code.google.com/p/v8/issues/detail?id=2825
I'm also baffled that more developers don't have a problem with this. I
can't believe this is still a problem. I can't get the suggested
workarounds to do anything, either. Are there more explicit instructions I
can try? I have tried adding --js-flags="--nolazy" to my system's shell
script that runs chrome, and no difference. Pretty hard to debug a problem
that only shows in Chrome, and not Firefox when I can debug fine in
firefox, but I can't because breakpoints aren't correct in Chrome. I love
developing in Chrome with the debugging tools, but if something like this
isn't fixed after so long, it makes me think people must just not use
chrome anymore, and forces me to focus on Firefox for developing, which I
would rather NOT do.
--
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.
