|
From: Bart V. A. <bar...@gm...> - 2009-04-14 09:11:18
|
On Tue, Apr 14, 2009 at 12:14 AM, Nicholas Nethercote <n.n...@gm...> wrote: > On Mon, Apr 13, 2009 at 10:06 PM, Konstantin Serebryany > >> Add http://software.intel.com/en-us/intel-parallel-studio-home/ to this list. >> A PIN-based hybrid of Memcheck and Helgrind, works on windows. Beta is free. > > On the Memcheck side, it looks like it's just a leak detector. When starting Intel's Parallel Inspector, one must choose between memory checking and thread checking. For memory checking, there is a choice between four different levels: * memory leak detection only. * memory access checking with call stack depth limit 1. * memory access checking with call stack depth limit 12. * enable all checks supported by the tool. My experience with beta 2 of Intel's Parallel Inspector is that it is considerably slower than Purify or BoundsChecker, and that it reports too much false positive reads of uninitialized variables (about hundred for a program where Purify reported zero occurrences). This tool e.g. already complains when copying a struct that contains uninitialized padding bytes. Bart. |