Opened 11 years ago
Closed 10 years ago
#1890 closed defect (wontfix)
JS Debugger hooks are per runtime
| Reported by: | Yves | Owned by: | Yves |
|---|---|---|---|
| Priority: | Nice to Have | Milestone: | Alpha 16 |
| Component: | Non-game systems | Keywords: | debugger, javascript, spidermonkey |
| Cc: | Patch: |
Description
The Javascript debugger (see JavascriptDebuggingServer) associates one ThreadDebugger instance with each ScriptInterface object. A ThreadDebugger registers its own hooks for traps, new scripts etc. at the Spidermonkey runtime level. The problem is that we have two ScriptInterfaces that are associated with the same runtime in the classes CAIPlayer and CAIWorker. The second hook will overwrite the first and this results in compartment mismatches and undefined behaviour. I will look at this problem while upgrading Spidermonkey because I first have to check if the one to one relation between Spidermonkey contexts and ScriptInterface objects is still valid.
Change History (4)
comment:1 by , 11 years ago
| Status: | new → assigned |
|---|
comment:2 by , 11 years ago
comment:3 by , 11 years ago
| Milestone: | Alpha 14 → Backlog |
|---|
comment:4 by , 10 years ago
| Milestone: | Backlog → Alpha 16 |
|---|---|
| Resolution: | → wontfix |
| Status: | assigned → closed |
Closing this as "wontfix" because the JS debugger will need a rewrite after the SpiderMonkey upgrade anyway. I know about this problem and there's no need to continue tracking this in a separate ticket.
Apparently there was a way to set per context debug hooks... was: https://bugzilla.mozilla.org/show_bug.cgi?id=730987