Lines Matching refs:stack
77 // from the calling function. When this function runs, the stack contains
148 // This test verifies that stack tracing works when called during
150 // TickSample::Trace uses Isolate::c_entry_fp as a starting point for stack
174 // When stack tracer is invoked, the stack should look as follows:
186 // Stack tracing will start from the first JS function, i.e. "JSFuncDoTrace"
191 context, "JSFuncDoTrace", sample.stack[base + 0]));
192 CHECK(IsAddressWithinFuncCode(context, "JSTrace", sample.stack[base + 1]));
196 // This test verifies that stack tracing works when called during
200 // pointer value as a starting point for stack walking.
203 // don't appear in the stack trace.
227 // When stack tracer is invoked, the stack should look as follows:
241 // Stack sampling will start from the caller of JSFuncDoTrace, i.e. "JSTrace"
244 CHECK(IsAddressWithinFuncCode(context, "JSTrace", sample.stack[base + 0]));
246 context, "OuterJSTrace", sample.stack[base + 1]));
275 // This test verifies that stack tracing doesn't crash when called on
