"Assertion failure: bug, at jsopcode.c:4834"

RESOLVED WORKSFORME

Status

()

--
critical
RESOLVED WORKSFORME
10 years ago
7 years ago

People

(Reporter: gkw, Unassigned)

Tracking

(Blocks: 1 bug, {assertion, testcase})

Trunk
x86
Mac OS X
assertion, testcase
Points:
---
Bug Flags:
in-testsuite ?

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

10 years ago
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?
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

10 years ago
This does not affect TM.
(Reporter)

Comment 3

10 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

10 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
Last Resolved: 10 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
Flags: in-testsuite?
(Reporter)

Updated

7 years ago
Flags: wanted1.9.0.x?
You need to log in before you can comment on or make changes to this bug.