Function call tracing is implemented using instrumentation
of the AOCL-BLAS code. Here, the functions are grouped based on their
position in the call stack. You can configure the level up to which
the traces must be generated. The default trace depth level is 5,
which will show, for example, calls down to gemm kernel level.
A lower level reduces the depth of the call stack used for a trace
generation.
Complete the following steps to enable and view the traces:
Enable the trace support and desired trace depth level, and build the AOCL-BLAS library as explained in Enabling Call Logging and/or Tracing.
Run the application to generate the trace data.
The trace output file for each thread is generated in the current folder.
The following figure shows a sample running the call tracing function using the test_gemm application:
Figure 4.5 Sample Run of Function Call Tracing#
The trace data for each thread is saved in the file with appropriate naming conventions. The .txt extension is used to signify the readable file:
P<process id>_T<thread id>_aocldtl_trace.txt
View the trace data.
The output of the call trace is in a readable format, you can open the file in any of the text editors. The first column shows the level in call stack for the given function.