Lines Matching full:trace
461 --trace-alloc. The former allows to detect reading from already freed
795 --trace-children=yes. An example:
812 - The format of some (non-XML) stack trace entries has changed a
1007 VALGRIND_PRINTF_BACKTRACE, the back-trace itself is considered
1399 * The limitation that you can't use --trace-children=yes together
1426 163955 remove constraint !(--db-attach=yes && --trace-children=yes)
1668 from --trace-mem has been made more compact, to reduce the size of the
1669 traces. Second, a new option --trace-superblocks has been added, which
1747 --trace-symtab-patt=<patt> limit debuginfo tracing to obj name <patt>
1748 --trace-cfi=no|yes show call-frame-info details? [no]
1899 n-i-bz BartV: Don't print more lines of a stack-trace than were obtained.
2003 * It has a new option --trace-mem (off by default) which causes it
2004 to print out a trace of all memory accesses performed by a
2184 automatically, even when using --trace-children and mixing execution
2425 while using --trace-children=yes. We hope to improve this situation
2694 96923 Zero sized arrays crash valgrind trace back with SIGFPE
3010 75099 impossible to trace multiprocess programs
