Comment #2 on issue 2369 by [email protected]: Debug: Provide special
breakpoint targets
http://code.google.com/p/v8/issues/detail?id=2369
Yury, I'd like to separately address the feature priority question and its
technical aspects.
On technical aspects here:
Script parsed event might be a good technique when you need to debug a
dynamically-loaded script with a poor name scheme – by having a breakpoint
with condition against script text you can efficiently filter out noise
scripts.
As to embedder events that could be simulated by JS/browser API, you assume
that browser is the only possible embedder. However, there are others (see
console appilcation use-case above), that would normally use Debug Agent
and have no actual communication with the remote debugger.
As to ScriptParsed event, it doesn't seem sufficient. First of all, for
Debug Agent it's asynchronous and cannot be used to make any required
preparations. Secondly, in Chromium approach you would need to handle
condition evaluation yourself, differently from what is done for
breakpoints. And again, even though ScriptParsed is synchronous for
Chromium, I'm not sure how far the callback is supposed to do arbitrary
processing, such as calling user JavaScript code (conditions).
However, there is a user-reported bug for Chromium:
http://code.google.com/p/chromium/issues/detail?id=156556
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
