Lines Matching full:trace
55 // - With --stack=yes, want to add a stack trace for detailed snapshots so
86 // - (Andy Lin) Give a stack trace on detailed snapshots?
515 // execution context ("XCon"), ie. a stack trace. (And sub-paths represent
854 // Get the stack trace for an XCon, filtering out uninteresting entries:
858 // Nb: it's possible to end up with an empty trace, eg. if 'main' is marked
872 // - If the original stack trace is smaller than asked-for, redo=False
875 // In other words, to redo, we'd have to get a stack trace as big as we
882 // alloc-fns to be removed from the stack trace.
893 // If the original stack trace is smaller than asked-for, redo=False.
980 // This allows a stack trace to be a sub-trace of another, eg. a/b/c is a
981 // sub-trace of a/b/c/d. So we can't assume this xpt is a bottom-XPt;
986 // test case that exhibit such a malformed stack trace, so I can't
998 "Warning: Malformed stack trace detected. In Massif's output,\n");
