Quantcast
Channel: C#
Viewing all articles
Browse latest Browse all 1853

Workflows-Quick Paths to Maximizing Productivity

$
0
0

There are many ways to take advantage of the power and flexibility of the Intel® Inspector.

Use the following workflows to help you maximize your productivity as quickly as possible. See links below for more details on each workflow.

Typical Workflows

Usage

Dynamic Analysis

Use the graphical user interface (GUI) to:

  1. Inspect a running application for issues and collect a result.

  2. Investigate the result.

  3. Fix issues that should not remain in source code.

Attention

Static analysis is deprecated. It may be removed in a future major release. If you have concerns or feedback, please comment at https://software.intel.com/en-us/static-analysis-deprecation.

Static Analysis

  1. Use an Intel studio compiler to inspect source code for issues and collect a result.

  2. Use the GUI to investigate the result and fix issues that should not remain in source code.

Note

Static analysis requires your code to compile without serious errors using an Intel® compiler. The results of this compilation cannot be executed. (Intel compilers operate in a special mode when performing static analysis: they dedicate more time to analysis and bypass the instruction generation process entirely. This allows them to find errors that go undetected during ordinary compilation.) Therefore, you can use static analysis even if you do not plan to use an Intel compiler to build your production binaries.

Reporting

Use the command line interface (CLI) to:

  1. Inspect a running application for issues and collect a result.

  2. Investigate the result.

Regression Testing

  1. Create a gold standard:

    • Use the GUI (or CLI) to create a result from which you have successfully eliminated all real problems.

    • Use the CLI to create a suppression file to match any remaining problems you have determined you can ignore.

  2. Change your source code.

  3. Use the CLI (or GUI) to check for new problems:

    • Apply the suppression file when you run a new analysis.

    • Determine if the changed source code introduced new problems that do not match those in the suppression file.

Inglese

Viewing all articles
Browse latest Browse all 1853

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>