Summary
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.
This tutorial demonstrated an end-to-end workflow you can ultimately apply to your own applications.
Step |
Tutorial Recap |
Key Tutorial Take-aways |
|---|---|---|
1. Set up |
If you used the Visual Studio* IDE: You chose a project, verified the project is set to produce the most accurate and complete analysis results, and built and ensured the application runs on your system outside the Intel Inspector. If you used the standalone GUI: You built the application using optimal compiler/linker settings, ensured the application runs on your system outside the Intel Inspector, set up the Intel Inspector environment, and created a project to hold analysis results. |
Applications compiled and linked in debug mode using the following options produce the most accurate and complete analysis results: /Zi or /ZI, /Od, /MD or /MDd, and no /RTC. |
2. Collect result |
You chose an analysis type and ran an analysis. During analysis, the Intel Inspector:
|
|
3. Investigate result |
You explored detected problems, interpreted the result data, accessed an editor directly from the Intel Inspector, and changed source code. |
|
4. Check your work |
You recompiled, relinked, and reinspected the application. |
Next step: Prepare your own application(s) for analysis. Then use the Intel Inspector to find and fix errors.