js/src/jit-test/tests/debug/cross-context-1.js@129ffea94266
js/src/jit-test/tests/debug/cross-context-1.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 // frame.eval can evaluate code in a frame pushed in another context. Bug 749697.
3 // In other words, the debugger can see all frames on the stack, even though
4 // each frame is attached to a particular JSContext and multiple JSContexts may
5 // have frames on the stack.
7 var g = newGlobal();
8 g.eval('function f(a) { debugger; evaluate("debugger;", {newContext: true}); }');
10 var dbg = new Debugger(g);
11 var hits = 0;
12 dbg.onDebuggerStatement = function (frame1) {
13 dbg.onDebuggerStatement = function (frame2) {
14 assertEq(frame1.eval("a").return, 31);
15 hits++;
16 };
17 };
19 g.f(31);
20 assertEq(hits, 1);
