Debug Logging - 5.2 English - 57404

The debug logging works very similar to the function call tracing and uses the same infrastructure. However, it can be enabled independent of the trace feature to avoid cluttering of the overall debugging information. This feature is primarily used to print the input values of the AOCL-BLAS APIs.

Complete the following steps to enable and view the debug logs:

1. Enable the debug log support and build the AOCL-BLAS library as explained in Enabling Call Logging and/or Tracing.

2. Run the application to generate the trace data.

   The trace output files for each thread is generated in the current folder.

   The following figure shows a sample running of AOCL-BLAS with the debug logs enabled using the test_gemm application:

   

   The debug logs for each thread are 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_log.txt

3. View the debug logs.

   The output file of the debug logs is in a readable format, which you can open in any text editor. The following figure shows the sample output for one of the threads of the test_gemm application:

   $ cat P3386555_T0_aocldtl_log.txt
   dgemm_blis_impl D N N 4000 4000 4000 1.300000 0.000000 4000 4000 0.700000 0.000000 4000 nt=1 911.148 ms 70.482 GFLOPS
   dgemm_blis_impl D N N 4000 4000 4000 1.300000 0.000000 4000 4000 0.700000 0.000000 4000 nt=8 121.024 ms 557.641 GFLOPS