Confirmed users
496
edits
Platform/JSDebugv2: Difference between revisions
→Long-term goals
| Line 9: | Line 9: | ||
* Now that SpiderMonkey is C++, an interface designed in that language can be more expressive and less error-prone than a C interface. | * Now that SpiderMonkey is C++, an interface designed in that language can be more expressive and less error-prone than a C interface. | ||
= | = General goals = | ||
* The interface must operate at the source language level, and not expose details of the implementation technique: it should behave the same way regardless of whether the debuggee is being executed by a bytecode interpreter (SpiderMonkey classic), a just-in-time compiler (TraceMonkey), or a whole-method JIT (Jägermonkey). If the implementation compiles to native code, the debugging interface should be independent of the underlying processor architecture. The interface should be sufficiently high-level to allow debugging of (say) JITted code without requiring the implementation to pretend that is still a bytecode interpreter. | * The interface must operate at the source language level, and not expose details of the implementation technique: it should behave the same way regardless of whether the debuggee is being executed by a bytecode interpreter (SpiderMonkey classic), a just-in-time compiler (TraceMonkey), or a whole-method JIT (Jägermonkey). If the implementation compiles to native code, the debugging interface should be independent of the underlying processor architecture. The interface should be sufficiently high-level to allow debugging of (say) JITted code without requiring the implementation to pretend that is still a bytecode interpreter. | ||