Closed
Bug 858170
Opened 12 years ago
Closed 12 years ago
Debugger crashes when handling an uncaught exception thrown by fireNewScript
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
FIXED
mozilla23
| Tracking | Status | |
|---|---|---|
| firefox22 | --- | fixed |
People
(Reporter: ejpbruel, Unassigned)
References
Details
(Keywords: crash)
Attachments
(1 file)
|
(deleted),
patch
|
jorendorff
:
review+
akeybl
:
approval-mozilla-beta+
|
Details | Diff | Splinter Review |
No description provided.
|
Reporter | |
Comment 1•12 years ago
|
||
Attachment #733477 -
Flags: review?(jorendorff)
|
||
Comment 2•12 years ago
|
||
Comment on attachment 733477 [details] [diff] [review]
Quick fix + test
Review of attachment 733477 [details] [diff] [review]:
-----------------------------------------------------------------
Yep. Thank you.
Attachment #733477 -
Flags: review?(jorendorff) → review+
|
|
Reporter | |
Comment 3•12 years ago
|
||
|
||
Comment 4•12 years ago
|
||
Status: NEW → RESOLVED
Closed: 12 years ago
Flags: in-testsuite+
Resolution: --- → FIXED
Target Milestone: --- → mozilla23
|
||
Updated•12 years ago
|
|
|
||
Comment 6•12 years ago
|
||
There are still crashes in 22.0a2. Any plan to uplift the patch?
|
||
Comment 7•12 years ago
|
||
Comment on attachment 733477 [details] [diff] [review]
Quick fix + test
I'll do the honors.
[Approval Request Comment]
Bug caused by (feature/regressing bug #): not sure, but I spotted this after bug 820012
User impact if declined: crashes when the JavaScript debugger is used
Testing completed (on m-c, etc.): m-c
Risk to taking this patch (and alternatives if risky): low risk, tiny patch, long bake time in m-c
String or IDL/UUID changes made by this patch: none
Attachment #733477 -
Flags: approval-mozilla-beta?
|
||
Comment 8•12 years ago
|
||
Comment on attachment 733477 [details] [diff] [review]
Quick fix + test
Early enough in the cycle to take this.
Attachment #733477 -
Flags: approval-mozilla-beta? → approval-mozilla-beta+
|
|
||
Comment 9•12 years ago
|
||
You need to log in
before you can comment on or make changes to this bug.
Description
•