Command Line Interface
When you use several features together, the executable produces a multiplexed trace file, containing several outputs targeting different features from Test RealTime.
The method for splitting the trace dump file is different, depending on the output file produced.
Memory Profiling for Java uses a .jpt JVMPI trace dump file.
All other features use an atlout.spt SCI dump file.
In most cases, you must split the atlout.spt trace file into several files for use with each particular Report Generator or the product GUI.
To do this, you must have a working perl interpreter. You can use the perl interpreter provided with the product in the /bin directory.
To split the trace file:
Use the atlsplit tool supplied in the /bin directory of Test RealTime :
atlsplit atlout.spt
After the split, depending on the selected runtime analysis tools, the following file types are generated:
.rio test result files: process with a Report Generator
.tio Code Coverage report files: view with Code Coverage Viewer
.tdf dynamic trace files: view with UML/SD Viewer
.tpf Memory Profiling report files: view with Memory Profiling Viewer
.tqf Performance Profiling report files: view with Performance Profiling Viewer
The Memory Profiling for Java features produces a .jpt file. When opening this file for the first time, the .jpt must be split into a .tpf file and a .txf file by studio.
To split and view the Java trace file:
Run the studio GUI with the following parameters:
studio <jpt file> <txf file> <tpf file>
After the split, depending on the selected runtime analysis tools, the following file types are generated:
.tpf Memory Profiling report files: view with Report Viewer
.txf Java Dynamic report files: view with Report Viewer
Related Topics
TDF Splitter - attsplit