Trace File Parsing
Description
Parse the trace file.
To obtain a .bin trace file, see Viewing Trace Logs in Log Reference.
Applicability
|
Product |
Supported |
|---|---|
|
Atlas 350 Accelerator Card |
√ |
|
|
√ |
|
|
√ |
|
|
√ |
|
|
√ |
|
|
√ |
Command
asys analyze -r=trace --file=filename --output=path
Parameters
- r: (mandatory) parsing mode. Set it to trace to parse trace log files (*.bin files) into .txt files. The version of the environment where the asys tool is used must be the same as that of the environment where trace logs are generated.
- file: used to parse a single file. Set this parameter to the file name containing the path. This parameter is mandatory in trace mode.
- output (optional): Its value is used as the prefix of the result output directory of the asys tool. That is, the final output directory is {output}/asys_output_timestamp. If the command does not contain the output parameter, the output is stored in the command execution directory. If the value of output is empty or invalid, the specified directory does not have the write permission, or the directory fails to be created, the asys tool exits and reports an error.
Usage Example and Output Description
asys analyze -r=trace --file=schedule_tracer_demo.bin --output=$HOME/dfx_info
The following is an example of the parsed .txt file:
2024-05-09 19:08:12.408.800 demo0: tid0[0], count0[0], tag0[struct0 tag], streamId0[0], deviceIdArray0[0, 1], hostIdArray0[1, 2, 3, 4] 2024-05-09 19:08:12.408.804 demo1: tag1[struct1 tag], streamId1[0], deviceIdArray1[0, 1], hostIdArray1[1, 2, 3, 4]
Parent topic: asys Tool Usage Guide