js/src/jit-test/tests/debug/cross-context-1.js@6474c204b198 (annotated)
js/src/jit-test/tests/debug/cross-context-1.js
Wed, 31 Dec 2014 06:09:35 +0100
- author
- Michael Schloh von Bennewitz <michael@schloh.com>
- date
- Wed, 31 Dec 2014 06:09:35 +0100
- changeset 0
- 6474c204b198
- permissions
- -rw-r--r--
Cloned upstream origin tor-browser at tor-browser-31.3.0esr-4.5-1-build1
revision ID fc1c9ff7c1b2defdbc039f12214767608f46423f for hacking purpose.
| michael@0 | 1 | // frame.eval can evaluate code in a frame pushed in another context. Bug 749697. |
| michael@0 | 2 | |
| michael@0 | 3 | // In other words, the debugger can see all frames on the stack, even though |
| michael@0 | 4 | // each frame is attached to a particular JSContext and multiple JSContexts may |
| michael@0 | 5 | // have frames on the stack. |
| michael@0 | 6 | |
| michael@0 | 7 | var g = newGlobal(); |
| michael@0 | 8 | g.eval('function f(a) { debugger; evaluate("debugger;", {newContext: true}); }'); |
| michael@0 | 9 | |
| michael@0 | 10 | var dbg = new Debugger(g); |
| michael@0 | 11 | var hits = 0; |
| michael@0 | 12 | dbg.onDebuggerStatement = function (frame1) { |
| michael@0 | 13 | dbg.onDebuggerStatement = function (frame2) { |
| michael@0 | 14 | assertEq(frame1.eval("a").return, 31); |
| michael@0 | 15 | hits++; |
| michael@0 | 16 | }; |
| michael@0 | 17 | }; |
| michael@0 | 18 | |
| michael@0 | 19 | g.f(31); |
| michael@0 | 20 | assertEq(hits, 1); |
