collect
Run the specified type of analysis and
collect data.
Syntax
-collect
<analysis_type>
-c
<analysis_type>
- Both short names and long names are case-sensitive. For example,-cis the short name of thecollectaction, and-Cis the short name of thecommandaction.
- To duplicate an analysis performed in theIntel InspectorGUI: Use theCommand Linebutton on theAnalysis Typewindow panes to copy the exact command to the clipboard.
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 storedin the specified or default-namedr@@@{at}result directory in the current working directory, where@@@represents the next available number and{at}represents theanalysis type with preset configuration.
- Finalization occurs automatically unless overridden.
- By default, a Summary report is displayed tostdoutand written to a .txt file in the current working directory.
Example
This command:
- Runs aDetect Deadlocks and Data Races (ti2)analysis on the applicationmyApp.
- Stores the result in the defaultr@@@ti2result directory in the current working directory, where@@@represents the next available number.
- Generates a summary report of detected problems, and writes it to theinspxe-cl.txtfile 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