Intel® Inspector Tutorial: Analyzing Memory Errors in a C++ Sample Application for Linux* OS

Tutorial

  • 2021.1
  • 12/04/2020
  • Public Content
Contents

Choose Problem

Intel® Inspector
 is a dynamic memory and threading error checking tool for users developing serial and multithreaded applications on Windows* and Linux* operating systems. This topic is part of a
tutorial
 that shows how to find and fix
memory
 errors using the
Intel Inspector
 and a
C++
 sample application.

Understand Key Terms

code location
: A fact the
Intel Inspector
 observes at a source code location, such as a
write
 code location. Previously called an
observation
.
problem
: One or more occurrences of a detected issue, such as an uninitialized memory access. Multiple occurrences have the same call stack but a different thread or timestamp. You can view information for a problem as well as for each occurrence.
problem set
: A group of problems with a common problem type and a shared code location that might share a common solution, such as a problem set resulting from deallocating an object too early during application execution. You can view problem sets only after analysis is complete.
See the Intel® Inspector Glossary for more key terminology.

Understand Summary Window Panes

A
Summary
 window similar to the following automatically displays after analysis completes successfully.
Summary window
1
The
Summary
 window is the starting point for managing result data. It groups problems into problem sets and then prioritizes the problem sets by severity and size.
2
Think of the
Problems
 pane as a
to-do
 list. Start at the top and work your way down. Try viewing the problems in various problem sets by clicking the corresponding by clicking the corresponding Expand control icon.
3
The
Code Locations
 pane shows the code location summary, surrounding source code snippet, and call stack information for all code locations in one or all occurrences of the problem(s) highlighted in the
Problems
 pane.
Try using the various controls on the slider to view information for different occurrences of the highlighted problem.

Choose a Problem

When you are finished experimenting, double-click the data row for the
Mismatched allocation/deallocation
 problem set
in the
find_and_fix_memory_errors.cpp
 source file
 to display the
Sources
 window, which provides more visibility into the cause of the error.

Product and Performance Information

1

Performance varies by use, configuration and other factors. Learn more at www.Intel.com/PerformanceIndex.