collect

Run the specified type of analysis and collect data.

Syntax

-collect <analysis_type>

-c <analysis_type>

Note

Both short names and long names are case-sensitive. For example, -c is the short name of the collect action, and -C is the short name of the command action.

Arguments

Memory error analysis types

Analysis type code Description
mi1

Memory error analysis that answers the question Does my target leak memory?

mi2

Memory error analysis that answers the question Does my target have memory access problems?

mi3

Memory error analysis that answers the question Where are the memory access problems?

Threading error analysis_types

Analysis type code Description
ti1

Threading error analysis that answers the question Does my target have deadlocks?

ti2

Threading error analysis that answers the question Does my target have deadlocks or data races?

ti3

Threading error analysis that answers the question Where are the deadlocks or data races?

Description

Use the collect action to run a memory or threading error analyis.

  • The result is stored in the specified or default-named r@@@{at} result directory in the current working directory, where @@@ represents the next available number and {at} represents the analysis type with preset configuration.

  • Finalization occurs automatically unless overridden.

  • By default, a Summary report is displayed to stdout and written to a .txt file in the current working directory.

Example

This command:

  • Runs a Detect Deadlocks and Data Races (ti2) analysis on the application myApp.

  • Stores the result in the default r@@@ti2 result directory in the current working directory, where @@@ represents the next available number.

  • Generates a summary report of detected problems, and writes it to the inspxe-cl.txt file in the result directory.

$ inspxe-cl -collect ti2 -- myApp

This command performs the same type of analysis as that above, but exits without finalizing the result or generating a summary report.

$ inspxe-cl -c ti2 -no-auto-finalize -- myApp

See Also


Supplemental documentation specific to a particular Intel Studio may be available at <install-dir>\<studio>\documentation\ .

For more complete information about compiler optimizations, see our Optimization Notice.