Closed Bug 740552 Opened 13 years ago Closed 1 year ago

[jsdbg2] Implement uncaughtExceptionHook as described in specification

Categories

(Core :: JavaScript Engine, enhancement)

Product:
Core
Component:
JavaScript Engine
Type:
enhancement

Tracking

()

Status:
RESOLVED INACTIVE

People

(Reporter: Gijs, Unassigned)

References

Details

STR: 1. Attach a Debugger() instance to a window. 2. Set an onEnterFrame hook 3. Have an exception thrown in your onEnterFrame hook ER: debuggee code completes AR: debuggee code doesn't get called I'm not sure this problem exists for other dbg2 hooks. In any case, IMHO this shouldn't happen.
Egh, this goes in the "I'm an idiot" bucket; I missed the note about the uncaughtExceptionHook in the docs. I still think the default there should be set. Twiddling bits about this bug for that purpose.
Severity: normal → enhancement
Summary: Exceptions from JS Debugging API listeners shouldn't break debuggee → Set Debugger.uncaughtExceptionHook to something useful by default
Yeah --- there are some unfinished bits there. The spec says that we throw a nice, informative error that confesses the debugger's failure, and includes the original exception object. The reality is that we just terminate the debuggee. Bug 729592 describes some preparation needed to implement the prescribed behavior.
Depends on: 729592
I believe the specified behavior for uncaughtExceptionHook would address the original problem (silent failure) in this bug, so I've changed the summary.
OS: Mac OS X → All
Hardware: x86 → All
Summary: Set Debugger.uncaughtExceptionHook to something useful by default → [jsdbg2] Implement uncaughtExceptionHook as described in specification
Assignee: general → nobody
Severity: normal → S3
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.