Closed
Bug 453982
Opened 16 years ago
Closed 16 years ago
"Assertion failure: bug, at jsopcode.c:4834"
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: gkw, Unassigned)
Details
(Keywords: assertion, testcase)
x = this
this.__defineSetter__("x", x.watch)
eval("function x ()(x)", x)--
shows:
Assertion failure: bug, at jsopcode.c:4834
opt works as expected. 1.9.0.x branch.
Flags: wanted1.9.0.x?
Comment 1•16 years ago
|
||
We hit this because we end up in js_DVG on an op in the prolog (the JSOP_DEFFUN). I'm not really sure what the best way to fix this is, though removing the JS_NOTREACHED would let us just fallback (if not gracefully).
![]() |
Reporter | |
Comment 2•16 years ago
|
||
This does not affect TM.
![]() |
Reporter | |
Comment 3•16 years ago
|
||
(In reply to comment #2)
> This does not affect TM.
i.e., this does not affect TM branch js shell at all, doesn't matter if -j is enabled.
Summary: "Assertion failure: bug, at jsopcode.c:4834" → [1.9.0.x branch] "Assertion failure: bug, at jsopcode.c:4834"
![]() |
Reporter | |
Comment 4•16 years ago
|
||
(In reply to comment #3)
> (In reply to comment #2)
> > This does not affect TM.
>
> i.e., this does not affect TM branch js shell at all, doesn't matter if -j is
> enabled.
Resolving as WFM would be a better resolution.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
Summary: [1.9.0.x branch] "Assertion failure: bug, at jsopcode.c:4834" → "Assertion failure: bug, at jsopcode.c:4834"
Version: 1.9.0 Branch → Trunk
Updated•16 years ago
|
Flags: in-testsuite?
![]() |
Reporter | |
Updated•13 years ago
|
Flags: wanted1.9.0.x?
You need to log in
before you can comment on or make changes to this bug.
Description
•