Comment #23 on issue 2825 by [email protected]: breakpoint resolved to
incorrect location
http://code.google.com/p/v8/issues/detail?id=2825
#21, you can be sure that only a tiny minority of developers that have an
issue with this will bother to come here. The rest will either resort to
primitive console.log()'s, or switch to another browser altogether that's
capable of providing basic debugging functionality.
And yes, it's beyond comprehension how such a fundamental feature of the
debugging platform could not only break, but remain broken for so many
months (quickly approaching a year). I won't pretend to even have a clue
how the v8 team works, but the last public involvement with this bug was
last year (7 months ago).
All this time, I thought something in my sourcemaps was messing with the
breakpoints, but today I tried to set some on a non-minified file and got
the same result. And --js-flags="--nolazy" seems to have no effect.
Edit: Actually, it appears that some form of this bug has been around for
over 4 years (https://code.google.com/p/chromium/issues/detail?id=35894)...
--
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.
