Troubleshooting Command Line Usage
Command Line Interface
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:
1. Use
the
atlsplit tool supplied in the /bin directory of Test RealTime :
atlsplit atlout.spt
After the split, depending on the selected runtime analysis features, 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
Troubleshooting Command Line Usage
The following information might help if you encounter any problems when using the
command line tools.
Failure
Response
Compilation fails
Ensure that the selected Target Deployment Port matches your
compiler; there may be several Target Deployment Ports for
one OS, each of which targets a different compiler. If you are
unsure, you can check the full name of a Target Deployment
Port by opening any of the .ini files located in the Target
Deployment Port directory.
Compiler reports that
options.h is missing
Ensure that you have correctly prepared the options.h file, and
that this file is located in a directory that is searched by your
compiler (this is usually specified with -I or /I option on the
compiler command line).
Compiler reports that
TP.h file is missing
If you are compiling on a target different from the host where
the generated file has been produced, double-check the above
specific requirements to compilation on a different target.
If the compiler and C/C++ Test Script Compiler are executed
on the same machine, ensure you have not used the -NOPATH
option on the test compiler command line, and that the
ATLTGT environment variable was correctly set while the test
compiler was executed.
331
