Closed
Bug 429252
Opened 16 years ago
Closed 16 years ago
trap changes decompilation of "{ let x }"
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
VERIFIED
FIXED
People
(Reporter: jruderman, Assigned: crowderbt)
References
Details
(Keywords: testcase)
Attachments
(2 files)
2.56 KB,
text/plain
|
Details | |
5.23 KB,
patch
|
shaver
:
review+
shaver
:
approval1.9+
|
Details | Diff | Splinter Review |
js> function f() { { let x } } js> f function f() { { let x; } } js> trap(f, 0, "") js> f function f() { { let x; } let x; }
Assignee | ||
Comment 1•16 years ago
|
||
This is fixed by my WIP patch from bug 422137.
Assignee | ||
Updated•16 years ago
|
Status: NEW → RESOLVED
Closed: 16 years ago
Flags: in-testsuite?
Resolution: --- → FIXED
Comment 2•16 years ago
|
||
I'll check in when the tree reopens
Comment 3•16 years ago
|
||
/cvsroot/mozilla/js/tests/js1_7/decompilation/regress-429252.js,v <-- regress-429252.js initial revision: 1.1 This test fails on mac os x, leopard at least. debug: Assertion failure: ATOM_IS_STRING(atom), at jsinterp.c:4946 opt: bus error Note to self: the automation is not collecting the proper error messages.
Flags: in-testsuite?
Flags: in-testsuite+
Flags: in-litmus-
Comment 4•16 years ago
|
||
/cvsroot/mozilla/js/tests/public-failures.txt,v <-- public-failures.txt new revision: 1.70; previous revision: 1.69
Comment 5•16 years ago
|
||
centos5 x86_64: nada fedora6/centos i686 32bit: Assertion failure: (script)->objectsOffset != 0, at jsinterp.c:6489 fedora8 32bit: Assertion failure: (uint32)((atoms - script->atomMap.vector + ((uintN)(((regs.pc + 0)[1] << 8) | (regs.pc + 0)[2])))) < objects_->length crowder, do you want a new bug or reopen this one?
Assignee | ||
Comment 6•16 years ago
|
||
Let's keep it here.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 7•16 years ago
|
||
I really don't know what I was thinking with the previous patch. This logic must occur in DecompileCode (which is not recursive). Otherwise, we end up doing pointer math on the untraped "code", using an unmodified pc. This causes us to go out-of-bounds on the code array we're untrapping. This bug is very serious and should block.
Assignee | ||
Updated•16 years ago
|
Flags: blocking1.9?
Assignee | ||
Comment 8•16 years ago
|
||
I'll create a follow-up bug to introduce some assertions in jsdbgapi.c:js_UntrapScriptCode which would have saved us from this. I'd rather not do that here.
Comment 9•16 years ago
|
||
also js1_5/extensions/regress-429264.js
Comment on attachment 318295 [details] [diff] [review] undoing my silliness from the previous patch r+a=shaver, thanks for the diff showing the net-of-previous changes.
Attachment #318295 -
Flags: review?(shaver)
Attachment #318295 -
Flags: review+
Attachment #318295 -
Flags: approval1.9+
Assignee | ||
Comment 11•16 years ago
|
||
jsopcode.c: 3.313
Status: ASSIGNED → RESOLVED
Closed: 16 years ago → 16 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•