Dynamic analysis reveals subtle defects or vulnerabilities whose cause is too complex to be discovered by static analysis. Unlike static analysis, debugger integration lets you diagnose the problem and find the root cause. Intel Inspector finds latent errors on the executed code path plus intermittent and non-deterministic errors, even if the error-causing timing scenario does not happen.
Intel® Inspector 2017
Memory and Thread Debugger
- Save money: Find and root cause errors early―before you release
- Save time: Quickly debug intermittent races and deadlocks
- Save effort: No special builds―just use your normal build
Save Money and Deliver More Reliable Applications
Find errors early―when they are less expensive to fix. Intel® Inspector is an easy-to-use memory and threading error debugger for C, C++ and Fortran* applications that run on Windows* and Linux*. No special compilers or builds are required. Just use a normal debug or production build. Use the graphical user interface or automate regression testing with the command line. The user interface can be used standalone on both Windows and Linux or integrated with Microsoft Visual Studio*. Enhance productivity, cut costs, and speed time-to-market.
Intel Inspector takes you to the source locations of threading and memory errors and provides a call stack to help you determine how you got there.
Save Time: Find and Debug Intermittent and Non-Deterministic Errors
Race conditions like the one above are very difficult to diagnose without a tool because they are non-deterministic. They won’t occur every time. Intel Inspector detects the race or deadlock, and then breaks into a debugger just before the error occurs.
Easy - No Special Builds! Use Your Normal Debug or Optimized Build
Unlike other memory and threading analysis tools, Intel Inspector never requires any special recompiles for analysis. Just use your normal debug or production build. (Include symbols so we can map to the source.) This not only makes your workflow faster and easier, it increases reliability and accuracy.
This is made possible by Intel Inspector’s dynamic instrumentation of your binary. Competitive static analysis and compilation-based instrumentation techniques struggle with dynamically generated or linked code. Intel Inspector inspects all code―including third party libraries where the source is not available.
New for 2017
- Intel Inspector now runs native on 2nd generation Intel® Xeon Phi™ processors. Inspecting code optimized for Intel Xeon Phi on the same processor simplifies the development workflow.
- Intel Inspector now has full support for all C++11 language features including std::mutex and std::atomic.
- Identification of threading bugs just got even easier. Intel Inspector will now give the variable name in addition to the code line for threading errors. This includes global, static, and stack variables.
Specs at a Glance
| Processors | Intel® and compatible processors when analyzing applications containing Intel® instructions. Now running native on 2nd generation Intel® Xeon Phi™ processors. |
| Languages | C, C++, Fortran |
| Development Tools and Environments |
Compatible with compilers from vendors that follow platform standards (e.g. Microsoft, GCC, and Intel® compilers). Can be used standalone on both Windows and Linux or integrated with Microsoft Visual Studio. No special compilers or builds are required; just use a normal debug or production build. |
| Operating Systems | Windows and Linux (See Try and Buy to compare options.) |
For complete information, see the documentation and release notes.
For more complete information about compiler optimizations, see our Optimization Notice.
