2011/6/28 Clifford Heath <clifford.heath / gmail.com>:
> I see quite a few segfault bugs being reported.
>
> Does anyone use Purify, valgrind, or any such tools?
> I've used Purify extensively in the past, and regard it
> as an essential tool for any C or C++ development.
> Such tools should be *mandatory* for any widely-used
> code-bases.

I and some committers use valgrind, or some tools.

> Memory corruption bugs are often innocuous, causing
> no effects until a slight change, that can be years after,
> causes random and unrelated crashes to appear
> seemingly out of the blue. Even just re-linking with an
> updated C library, adding a function that affects memory
> layout (so a bug in *another* function shows up), and
> basically the tiniest changes, can trigger a fault to show
> itself.
>
> The only way to effectively prevent such bugs is a tool
> like Purify, which isolates the source of a potential
> error, possibly long before the subsequent crash.
> Purify is much better than valgrind, by the way. It rewrites
> your object code (including all system shared libraries)
> such that every memory reference is checked; no bounds
> overflows, no read-before-set errors, etc. An incredible and
> under-utilised tool...

If IBM gives us Purify, we may use it.

-- 
NARUSE, Yui naruse / airemix.jp>