Closed Bug 585540 Opened 15 years ago Closed 15 years ago

JM: Crash [@ js::mjit::JaegerShot]

Categories

(Core :: JavaScript Engine, defect)

defect
Not set
critical

Tracking

()

RESOLVED FIXED

People

(Reporter: gkw, Assigned: dvander)

References

Details

(Keywords: crash, regression, testcase)

Crash Data

try { (function () { gczeal(2)() })() } catch (e) {} (function () { for (y in [/x/, Boolean, Boolean, 0, Boolean]) { [Math.floor(this)].some(function () {}) } })() crashes js debug shell on JM changeset 703591778058 with -m at js::mjit::JaegerShot Program received signal SIGSEGV, Segmentation fault. 0xf76a8929 in ?? () (gdb) bt #0 0xf76a8929 in ?? () #1 0x08212a16 in js::mjit::JaegerShot (cx=0x8342c68) at ../methodjit/MethodJIT.cpp:696 #2 0x080d98dc in js::RunScript (cx=0x8342c68, script=0x8347c80, fun=0x0, scopeChain=0xf7502000) at ../jsinterp.cpp:466 #3 0x080da6d5 in js::Execute (cx=0x8342c68, chain=0xf7502000, script=0x8347c80, down=0x0, flags=0, result=0xffffd200) at ../jsinterp.cpp:954 #4 0x0806fc54 in JS_ExecuteScript (cx=0x8342c68, obj=0xf7502000, script=0x8347c80, rval=0xffffd200) at ../jsapi.cpp:4740 #5 0x0804c30a in Process (cx=0x8342c68, obj=0xf7502000, filename=0x0, forceTTY=0) at ../../shell/js.cpp:534 #6 0x0804ce99 in ProcessArgs (cx=0x8342c68, obj=0xf7502000, argv=0xffffd408, argc=1) at ../../shell/js.cpp:861 #7 0x08055666 in shell (cx=0x8342c68, argc=1, argv=0xffffd408, envp=0xffffd410) at ../../shell/js.cpp:5034 #8 0x08055782 in main (argc=1, argv=0xffffd408, envp=0xffffd410) at ../../shell/js.cpp:5130 (gdb) x/i $eip => 0xf76a8929: testl $0xffff0000,(%eax,%eax,1) (gdb) x/b $eax 0xf7502300: 0x60
Depends on: 585541
Blocks: 585541
No longer depends on: 585541
callprop patching is broken somewhere
Assignee: general → dvander
Status: NEW → ASSIGNED
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Crash Signature: [@ js::mjit::JaegerShot]
A testcase for this bug was automatically identified at js/src/jit-test/tests/jaeger/bug585540.js.
Flags: in-testsuite+
You need to log in before you can comment on or make changes to this bug.