Closed Bug 517349 Opened 15 years ago Closed 15 years ago

Remove incorrect assertion in js_TraceStackFrame

Categories

(Core :: JavaScript Engine, defect)

x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED FIXED
Tracking Status
status1.9.2 --- beta1-fixed

People

(Reporter: mrbkap, Assigned: mrbkap)

Details

(Whiteboard: fixed-in-tracemonkey)

Attachments

(1 file)

      No description provided.
Attached patch Fix (deleted) — Splinter Review
Attachment #401332 - Flags: review?(dvander)
Assignee: general → mrbkap
Attachment #401332 - Flags: review?(dvander) → review+
For what it's worth, this assertion is currently causing crashes running mochitest-browser-chrome on mozilla-central debug builds.  We're hitting a case where fp->regs is null, which means that we dereference null trying to evaluate the assertion that this patch removed:

            if (fp->regs && fp->regs->sp) {
                nslots = (uintN) (fp->regs->sp - fp->slots);
                JS_ASSERT(nslots >= fp->script->nfixed);
            } else {
                nslots = fp->script->nfixed;
                JS_ASSERT_IF(!fp->regs->sp, nslots == 0);
            }
Yeah, let's get it merged soon.  I wonder if people need to do their own merges for small/key stuff in addition to the more structured merges that sayrer does?
For mozilla-central, doing one's own landings would be easy and I'd do it myself, provided it's not going to mess up sayrer's merges and tree sync tracking.

I don't have the hg-fu to do the branch landings, but I could learn. mrbkap can do it, I've seen him ;-).

/be
I'm going to let sayrer take care of the full merge. I'll just cherry-pick this fix to m-c (the merge tools will do the Right Thing (TM)).
http://hg.mozilla.org/mozilla-central/rev/bc8bbb513d4e
Status: NEW → RESOLVED
Closed: 15 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: