Search results
Create the page "Trace" on this wiki! See also the search results found.
- aprobe -u trace my32bitapp.exe ap64 aprobe -u trace my64bitapp.exe24 KB (3,264 words) - 17:46, 13 September 2021
- aprobe -u trace my32bitapp.exe ap64 aprobe -u trace my64bitapp.exe25 KB (3,323 words) - 16:56, 4 October 2021
- aprobe -u trace my32bitapp.exe ap64 aprobe -u trace my64bitapp.exe25 KB (3,348 words) - 16:53, 16 February 2022
- aprobe -u trace my32bitapp.exe ap64 aprobe -u trace my64bitapp.exe25 KB (3,365 words) - 17:25, 8 September 2022
- === Stack Trace Support === ...eback functions and macros provide an easy mechanism for obtaining a stack trace--a list showing the current routine, the routine which called that, its cal74 KB (11,935 words) - 00:41, 11 March 2020
- ...probe code itself. The predefined probes such as [[Trace_Predefined_Probe|trace.ual]] check these. Use this macro in your probe to check the global trace-enabled count:102 KB (15,018 words) - 23:05, 27 February 2019
- ...Cause and have been using the GUI, you can use the Custom... button in the Trace Setup window to generate a probe, and look at that. If that looks too daunt The RootCause Trace Setup window shows a tree of all the functions organized by module, directo162 KB (25,627 words) - 17:12, 20 September 2021
- ...the coverage probe by calls from within their own probes. The API for the trace probe is defined by [../include/coverage.h <code>$APROBE/include/brcov.h</c36 KB (4,378 words) - 06:24, 20 March 2018
- ...the coverage probe by calls from within their own probes. The API for the trace probe is defined by [../include/coverage.h <code>$APROBE/include/coverage.h49 KB (6,266 words) - 18:19, 7 December 2022
- If you use the "trace.ual" predefined probe with the <code>SaveTraceDataTo APD_FILE</code> option aprobe -u trace.ual -d /tmp/trace-fred.apd fred39 KB (6,256 words) - 23:00, 27 February 2019