General runtime Analysis Settings

Selective instrumentation

By default, runtime analysis tools instrument all components of source code under analysis.

The Selective Instrumentation settings allow you to more finely define which units (classes or functions) you want to instrument and trace.

• Instrument inline methods: Extends instrumentation to inline methods.

• Instrument included methods or functions: Extends instrumentation to included methods or functions.

• Selective unit instrumentation:Click the...button to access a list of units (classes and functions) that can be explicitly selected for instrumentation. Click a unit to select or clear a unit. Use theSelect FileandClear Filebuttons to select and clear all units from a source file.

• Excluded files:Specifies a list of files that are parsed by the instrumentor, but are not instrumented. Click the ... button and use the Add and Remove buttons to select the files to be excluded.

• Excluded directories: Click the ... button and use the Add and Remove buttons to select the files to be excluded.

Advanced options

• Identification header: Select this option to add an identification header to files generated by the Instrumentor, including the command line used to generate the file, the version of the product, date and operating system information.

• Full template instrumentation: By default unused methods within a template are ignored by the Instrumentor. Set this option to Yes to analyze and instrument all template methods, even if they are not used.

• Application includes system files: Set this option to Yes if the application includes system files such as windows.h in Windows or pthread.h in UNIX.

• Internal data allocation: Select either Static declaration or Dynamic allocation as the memory allocation method for storing intermediate variables in the instrumented source code.

• Additional instrumentor options: This setting allows you to add command line options for the Instrumentor. Normally, this line should be left blank.

• Use alternate checksum: Select Yes to calculate a more unambiguous checksum for .fdc and .tsf files. Select No to remain compatible with existing .fdc and .tsf files. Before using this option, you must delete existing fdc and tsf files, which will be re-created with the new checksum. File keys are not changed by this option.

• Check internal data before use: Set this option to Yes if you are experiencing crashes of the application when Runtime Analysis is engaged. This option improves compatibility but increases memory usage.

• Generate TPM files: Set this option to Yes if you want to generate metrics for the test process monitor.

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.

For each tab, click the ... button to open the function name selection box. Use the Add and Remove buttons to create a list of function names.

See Generating SCI Dumps for more information.

Static file storage

Depending on the runtime analysis feature, the product generates .tsf or .fdc temporary static data files during source code instrumentation of the application under analysis.

• Code Coverage static file storage (.fdc): These settings apply to Code Coverage .fdc static trace files:

• • Build Directory: Select this option to use the current directory for all generated files.

  • Other Directory: Select this option to define a specific directory.

  • Source Directory: Select this option to use the same directory as the source under analysis.

  • Use Single Temporary File (.fdc): By default, Code Coverage produces one .fdc file for each instrumented source file. Select this option to use a single .fdc file for all instrumented source files, and specify its location.

• FDC Directory or Name: When using the Use single temporary file (.fdc)option in the previous setting, specify a location for the.fdcfile.

• Memory Profiling, Performance Profiling, and Runtime Tracing storage: This setting applies to Memory Profiling, Performance Profiling and Runtime Tracing .tsf static trace files.

• • Build directory: Select this option to use the current directory for all generated files.

  • Other directory: Select this option to define a specific directory.

  • Source directory: Select this option to use the same directory as the source under analysis.

  • Use single temporary file (.tsf): By default, Memory Profiling, Performance Profiling and Runtime Tracing produces one .tsf file for each instrumented source file. Select this option to use a single .tsf file for all instrumented source files, and specify its location.

• TSF directory or name: When using the Use single temporary file (.tsf)option in the previous setting, specify a location for the.tsffile.

To edit the General Runtime Analysis 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, expand Runtime Analysis and select General.

4. Select Snapshot, Selective Instrumentation, Static File Storage or Miscellaneous.

5. When you have finished, click OK to validate the changes.

Related Topics

Using Runtime Analysis Features | Configuration Settings