Specifications

System Software Diagnostics Guide — September 2006 43
Debugging Software
configuration file. The RTF tracing capabilities are turned on by default. Refer to
Section 28.3.1, “RTFConfig Tag”, on page 143 for complete information about the
RTFConfig tag. The RTFConfig tag includes the following child tags:
• Logfile: This is the first child tag of the RTFConfig tag. The Logfile tag’s attributes set the
parameters for the RTF logfile output. This tag is an optional part of the RTF
configuration file. Refer to Section 28.3.2, “Logfile Tag”, on page 145 for complete
information about the Logfile tag.
• Global: This is the second child tag of the RTFConfig tag. The Global tag is used to
specify the global configuration. Configuration settings at the global level are valid for all
modules in the RTF configuration file. When a module is traced at the global level, all
activity related to that particular module is traced. However, global tag settings have the
lowest priority; they can be override by settings in individual Module tags. Refer to
Section 28.3.3, “Global Tag”, on page 147 for complete information about the Global tag.
• Module: This is the third child tag of the RTFConfig tag. The Module tag is used to
specify the trace configuration for a particular module. The default RTF configuration
contains pre-defined module tags for traceable runtime libraries. You can edit the state
attributes of these pre-defined module tags or delete these pre-defined module tags. The
default setting for each module’s state attribute is 1, meaning that tracing is enabled by
default for each module in the .xml file. If you choose to delete modules, keep in mind that
the RtfConfigLinux.xml and RtfConfigWin.xml files must contain at least one Module tag.
Refer to Section 28.3.7, “Module Tag”, on page 150 for complete information about the
Module tag.
4. When you are finished editing the RTF configuration file, save and close the file.
5. Start your application. As your application runs, RTF will trace the runtime libraries according
to RTF configuration file settings. Refer to the individual entries in the log file or debug stream
to review the trace statements generated by the runtime libraries.
6. If you wish to dynamically edit the RTF trace levels while your application runs, it is not
necessary to stop the RTF. Instead, perform the following:
1. Open the RTF configuration file.
2. Customize the settings in the RTF configuration file.
3. Save and close the RTF configuration file.
4. Issue the
rtftool reload command to reload RTF configuration file and restart the
RTF engine.
Note: Keep in mind that changes made to the RTF configuration file will not be reflected in
the RTF output until the tool has been reloaded.
7. At any time, you can issue the
rtftool command to pause/restart RTF. RTF will not provide
trace output while it is paused.
• For more information about RTF and manually editing the configuration file, refer to
Chapter 28, “Runtime Trace Facility (RTF) Reference”.
Note: If you run full RTF logging on high-density systems (1000 media channels), you may experience
I/O throughput degradation. It is recommended that you do not run RTF with full logging on high-
density systems or any field-deployed systems. Instead, use runtime filtering capabilities of the
RTF to only log the data you are interested in.