Datasheet

Top Features
Choose Your Level - Go Fast or Be Thorough
The first level of analysis has very little overhead. Use it during
development because it is fast. The second level (shown) takes
more time and detects more issues. It is often used before
checking in a new feature. The third level is great for regression
testing and finding bugs.
Debugger Breakpoints Simplify Diagnosis
Debugger breakpoints make it easier to diagnose difficult errors
by breaking into the debugger just before the error occurs.
Examine variables and look at other threads to diagnose the
problem. Microsoft Visual Studio*, GDB and IDB debuggers are
supported. Just select the error and choose “Debug This
Problem” from the pop-up menu.
Analyze Heap Growth + New “Instant” leak report
Puzzled about what is causing your memory use to grow and
grow as your app continues to run? Heap growth analysis helps
you diagnose the cause. Get an instant heap growth report of
allocations not deallocated since the last baseline. New! Now
you can also get an instant report of leaks since the last baseline.
Speed Analysis with Pause/Resume
__itt_suppress_push(__itt_suppress_threading_errors);
/* Any threading errors here will be ignored */
__itt_suppress_pop();
/* Any threading errors here will be seen */
Pause/Resume Speeds Up Analysis
Speed-up analysis by limiting its scope. Turn on analysis only
during the execution of the suspected problem. Instrumentation
overhead is reduced to speed through long irrelevant sections of
code. Used carefully, this can be very powerful in situations
where long run times are required to reach the error.
Precise Suppressions Remove False Errors Safely
Suppression = {
Name = "Example";
Type = { uninitialized_memory_access }
Stacks = {
{
mod=a.out, func=update_x;
func=main;
Suppress False Errors, Share with the Team
False errors are easily added to a suppression list so you don’t
need to investigate them next time. Multiple lists are supported
and can be shared with other project members. Create your own
private suppressions to block errors that are not in your code.
Suppressing an entire module can also reduce collection time.
Team Collaboration
Each error reported contains state information (New, Confirmed,
Fixed, Not Fixed, Regression, Not a Problem, Deferred) to help
you sort and prioritize errors. State information from multiple
developers can now be merged and shared. Users can optionally
comment on errors to explain why a certain state was set.
Filters Manage the Error List
Just want to see the errors from your source file? Just click and
only those errors are shown. Working through the new errors
and only want to see the highest severity? Just click. Filters are
available for many categories: Severity, problem type, state,
module, etc. They weed out the noise and let you focus on what
is most important.
Find difficult to diagnose out-of-bounds accesses
Pointer Checker** is a compiler-based diagnostic that traps
memory accesses beyond allocated addresses.Find dangling
pointers, buffer overflows, etc. Speed-up diagnosis by breaking
into the debugger when the exception occurs.
**Bonus feature available when purchased as a part of one of the Intel® Parallel Studio XE family of tool suites (see page 4).