Probe Control Settings
Graphical User Interface
By default, the settings of each node are inherited from those of the parent node.
When you override the settings of a parent node, changes are propagated to all child
nodes within the same Configuration. Overridden fields are displayed in bold.
Probe Control Settings
·
Probe Enable: This setting enables or disables the Trace Probe feature as
implemented with System Testing for C. See Trace Probes.
·
Probe Settings: These settings allow you to select the Probe macro mode.
·
Messaging API: Use the Add and Remove buttons to create a list of Messaging
API files. These are source files that define the structure declarations required
by Virtual Testers.
·
Replay Command Line Argument: Use this setting to send command line
arguments to the Trace Probe Perl script for advanced usage.
To edit the Probe Control settings for a node:
1. In
the
Project Explorer, click the Settings
button.
2.
Select a node in the Project Explorer pane.
3.
In the Configuration Settings list, select Probe Control.
4.
When you have finished, click OK to validate the changes.
Runtime Analysis Settings
The General Runtime Analysis settings are part of the Configuration Settings dialog
box, which allows you to configure settings for each node.
By default, the settings of each node are inherited from those of the parent node.
When you override the settings of a parent node, changes are propagated to all child
nodes within the same Configuration. Overridden fields are displayed in bold.
Snapshot Settings
In some case, such as with applications that never terminate or when working with
timing or memory-sensitive targets, you might need to dump traces at specifics
points in your code.
·
On Function Entry: Allows you to specify a list of function names, from your
source code, that will dump traces at the beginning of the function.
·
On Function Return: Allows you to specify a list of function names, from your
source code, that will dump traces at the end of the function.
·
On Function Call: Allows you to specify a list of function names, from your
source code, that will dump traces before the function is called.
273
