js/src/jit-test/tests/basic/testGuardCalleeSneakAttack2.js

Sat, 03 Jan 2015 20:18:00 +0100

author
Michael Schloh von Bennewitz <michael@schloh.com>
date
Sat, 03 Jan 2015 20:18:00 +0100
branch
TOR_BUG_3246
changeset 7
129ffea94266
permissions
-rw-r--r--

Conditionally enable double key logic according to:
private browsing mode or privacy.thirdparty.isolate preference and
implement in GetCookieStringCommon and FindCookie where it counts...
With some reservations of how to convince FindCookie users to test
condition and pass a nullptr when disabling double key logic.

     1 function loop(f, expected) {
     2    // This is the loop that breaks us.
     3    // At record time, f's parent is a Call object with no fp.
     4    // At second execute time, it is a Call object with fp,
     5    // and all the Call object's dslots are still JSVAL_VOID.
     6    for (var i = 0; i < 9; i++)
     7        assertEq(f(), expected);
     8 }
    10 function C(bad) {
    11    var x = bad;
    12    function f() {
    13        return x;  // We trick TR::callProp() into emitting code that gets
    14                   // JSVAL_VOID (from the Call object's dslots)
    15                   // rather than the actual value (true or false).
    16    }
    17    if (bad)
    18        void (f + "a!");
    19    return f;
    20 }
    22 var obj = {
    23 };
    25 // Warm up and trace with C's Call object entrained but its stack frame gone.
    26 loop(C.call(obj, false), false);
    28 // Sneaky access to f via a prototype method called implicitly by operator +.
    29 Function.prototype.toString = function () { loop(this, true); return "hah"; };
    31 // Fail hard if we don't handle the implicit call out of C to F.p.toString.
    32 C.call(obj, true);

mercurial