Comment #5 on issue 2369 by [email protected]: Debug: Provide special
breakpoint targets
http://code.google.com/p/v8/issues/detail?id=2369
Yang,
Debug.DebugEvent has its shortcomings. I want a full breakpoint semantics
and that's what's missing now:
- complete execution state (normal access to debug call stack)
- user condition expressions (an expression that is calculated in a special
scope with event parameters)
- DebugAgent protocol support. Someone who connects to V8 with DebugAgent
(e.g. Node.JS) does not have a direct access to javascript API. It will
only receive asynchronous notifications via protocol, as far as I
understand. Instead, user condition should be checked and if positive, the
full debug pause should be established.
As to immediate need, I meant this bug more like a roadmap – my view how we
could provide a consistent and feature-rich model for similar needs. I
didn't mean an immediate need, probably I should have written it more
explicit.
However, I think the workaround you are suggesting may not entirely fit
into debugger philosophy: basically you suggest user to modify his program.
But for example do one ever need conditional breakpoints with this
approach? I want to say that our JavaScript debugger tools clearly assume
that not always user can (or want to) modify his program. So I planned this
feature with the similar assumptions.
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
