Closed Bug 589340 Opened 14 years ago Closed 14 years ago

factor out / weaken dummy frames

Categories

(Core :: JavaScript Engine, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: luke, Assigned: luke)

Details

(Whiteboard: fixed-in-tracemonkey)

Attachments

(2 files, 1 obsolete file)

Attached patch patch (obsolete) — Splinter Review
According to Blake, the callee/fun of the dummy frame created in jsdbgapi.cpp is ignored by caps since its a native function.  Therefore, the dummy frames made by jsdbgapi.cpp are doing the same thing as those in jswrapper (providing a scopeChain so that cx->globalObject isn't used) and we can merge the two.  This is good because it puts the grossness into one place, and narrows the set of possibilities of what we can see in a frame, which is good for stack frame evisceration.

Patch passes trace/ref tests, will try-server soon.
Attached patch patchSplinter Review
Green on try.
Attachment #467951 - Attachment is obsolete: true
Attachment #468090 - Flags: review?(mrbkap)
Attachment #468090 - Flags: review?(mrbkap) → review+
Attached patch patchSplinter Review
http://hg.mozilla.org/tracemonkey/rev/b6179390c115

Minutes after I land I find that JSCrossCompartmentWrapper::{call,construct} are manually writing to vp[0] and vp[1].  Apparently nothing of value was in the fields of the dummy JSStackFrame being trampled...
Attachment #468991 - Flags: review?(mrbkap)
Attachment #468991 - Flags: review?(mrbkap) → review+
http://hg.mozilla.org/tracemonkey/rev/e81fa1f189dc
Whiteboard: fixed-in-tracemonkey
http://hg.mozilla.org/mozilla-central/rev/12e0e9006ef4
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: