Lines Matching refs:stack
76 // from the calling function. When this function runs, the stack contains
138 // This test verifies that stack tracing works when called during
140 // TickSample::Trace uses Isolate::c_entry_fp as a starting point for stack
163 // When stack tracer is invoked, the stack should look as follows:
174 // Stack tracing will start from the first JS function, i.e. "JSFuncDoTrace"
179 context, "JSFuncDoTrace", sample.stack[base + 0]));
180 CHECK(IsAddressWithinFuncCode(context, "JSTrace", sample.stack[base + 1]));
184 // This test verifies that stack tracing works when called during
188 // pointer value as a starting point for stack walking.
191 // don't appear in the stack trace.
214 // When stack tracer is invoked, the stack should look as follows:
227 // Stack sampling will start from the caller of JSFuncDoTrace, i.e. "JSTrace"
230 CHECK(IsAddressWithinFuncCode(context, "JSTrace", sample.stack[base + 0]));
232 context, "OuterJSTrace", sample.stack[base + 1]));
261 // This test verifies that stack tracing doesn't crash when called on
