Re: valgrind-3.5.0 is available (Mac OS X support)
Re: valgrind-3.5.0 is available (Mac OS X support)
- Subject: Re: valgrind-3.5.0 is available (Mac OS X support)
- From: Jonas Maebe <email@hidden>
- Date: Fri, 21 Aug 2009 18:54:25 +0200
On 21 Aug 2009, at 18:34, Sean McBride wrote:
Have you also used Apple's GuardMalloc and Instruments? Could you
comment on how they compare? Does one find bugs the other cannot?
Other pros/cons?
They're incomparable. Valgrand can track every single operation in
your program and for each check whether
a) it reads from a valid memory address (i.e., the stack, the data
segment, or a memory block allocated from the heap which has not been
freed since)
b) this operation *only* reads bits (yes, bits, not bytes) that have
been written previously, i.e., it can detect virtually all uses of
uninitialised data. It does this both for registers and for memory, so
it also works for e.g. register variables.
It can also detect memory leaks and with more accuracy than more blunt
tools that are not based on dynamic instrumentation, but that's not
really its main selling point imho.
Its only downside is obviously that it significantly slows down your
program, since it's basically recompiling the machine code at run time
into an instrumented version (rather than only intercepting a few
library calls or performing sampling). That's inherent to dynamic
instrumentation though, and Valgrind does already include various
optimizations to reduce the overhead as much as possible.
Jonas
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden