Closed Bug 723773 Opened 12 years ago Closed 12 years ago

Liveness analysis makes mistakes when analyzing try/catch

Categories

(Core :: JavaScript Engine, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla13
Tracking Status
firefox11 --- unaffected
firefox12 --- affected
firefox13 --- fixed
firefox-esr10 --- unaffected

People

(Reporter: billm, Assigned: billm)

References

Details

(Keywords: regression, Whiteboard: [advisory-tracking+])

Attachments

(1 file)

Attached patch patchSplinter Review
This was basically a mistake over the meaning of some arguments to the Lifetime constructor, I think. The fix is simple.

Most of the work of writing this patch was in figuring out the meaning of the savedEnd field, so I tried to improve the comment describing it. Let me know if you have any ideas for this.

I don't understand precisely how the JIT uses this information, so I decided to be conservative and close the bug.
Attachment #594024 - Flags: review?(bhackett1024)
Comment on attachment 594024 [details] [diff] [review]
patch

Review of attachment 594024 [details] [diff] [review]:
-----------------------------------------------------------------

Thanks!

::: js/src/jsanalyze.cpp
@@ +1008,5 @@
> +     *
> +     * Each time we create a Lifetime, we store the start of the most recently
> +     * seen sequence of conditional code in the Lifetime's savedEnd field. So,
> +     * when creating the Lifetime at #2, we set the Lifetime's savedEnd to
> +     * #5. (The most start of the most recent conditional is cached in each

rm 'most'
Attachment #594024 - Flags: review?(bhackett1024) → review+
From philor:
Backed out in https://hg.mozilla.org/integration/mozilla-inbound/rev/71f5bf4df2f6 - one of the six in that push was crashing in js::gc::Mark<JSString>
Target Milestone: mozilla13 → ---
https://hg.mozilla.org/mozilla-central/rev/3d8b2998c103
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
regression from bug 714645 which landed in Firefox 12 so we don't have to worry about ESR. Not sure if this is serious enough to warrant fixing on the beta branch.
What security rating should be attached to this issue?
Whiteboard: [advisory-tracking+]
Is there something QA can do to verify this fix?
Group: core-security
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: