----- Original Message -----
From: "chromatic" <[EMAIL PROTECTED]>
Sent: Saturday, March 15, 2008 10:45 PM
On Saturday 15 March 2008 13:40:13 Peter Gibbs wrote:
Incidentally, I found the following useful to stop valgrind
complaining
about uninitialized values causes by walking the stack:
Very nice. Do we need to compile with -DVALGRIND, or is there special
magic
somewhere?
Since the valgrind client requests are supposed to be very low overhead
when not running under valgrind, there should be no problem with adding
a configure step to define it (and set the correct library path, which I
just hardcoded), but I just used -DVALGRIND. That patch is not
committed, as I don't know if valgrind is used often enough to justify
it.
--
Peter
