PRACTICE Script Language User’s Guide | 17
©
1989-2024 Lauterbach
Logging the Call Hierarchy of PRACTICE Scripts
The call hierarchy of PRACTICE scripts (*.cmm) can be logged automatically or manually. In either case, the
log mechanism is based on the LOG.DO command.
During start-up of TRACE32, the PRACTICE script calls are always logged automatically. The log file
contents are output to an autostart log file in the temporary directory of TRACE32. On every start-up of
TRACE32, the previous autostart log file is overwritten and a new one is generated. The current autostart
log is accessible via the File menu in TRACE32.
In addition, you can manually log PRACTICE script calls at any time after TRACE32 has started. When you
initiate the log, you can choose folder and file name. To display the log file, use the TYPE or the EDIT
command on the TRACE32 command line.
To enable logging, use one of the following options:
• autostart.cmm: On start-up of TRACE32, the autostart.cmm is called automatically, and the
LOG.DO command in the autostart.cmm generates the autostart log file.
• --t32-logautostart: This command line option starts LOG.DO internally to generate an autostart
log file.
- This option is only needed (a) if you do not have the autostart.cmm or (b) if the script block
with the LOG.DO command has been deleted from the autostart.cmm.
- For a description of the command line options and an example for --t32-logautostart, refer to
“Command Line Arguments for Starting TRACE32” in TRACE32 Installation Guide, page
53 (installation.pdf).
Tip: To explicitly disable all PRACTICE script calls on start-up, use --t32-safestart.
• TRACE32 command line: Use the LOG.DO <file> command to generate your log file.
To access the autostart log file in TRACE32:
1. Start TRACE32 via T32Start.
The autostart.cmm generates the autostart log file automatically.
2. Choose File menu > Automatic Scripts on Start > View Autostart log.
The file opens in the TYPE window. The screenshot shows an example of an autostart log file:
A The file name convention of the autostart log is described below.
B The log file header tells you how the autostart log was generated.