[htdig-dev] Re: Testing Tasks

[Lachlan A. <lh...@us...>]

Greetings all,

Thanks, Neal, for your work setting up the tasks!

When I run  valgrind,  I get
=3D=3D4058=3D=3D Conditional jump or move depends on uninitialised value(=
s)
=3D=3D4058=3D=3D    at 0x40300421: CDB___lock_put_nolock (lock.c:650)
from various contexts.

I don't fancy changing the BDB code (my last foray was rather=20
forgettable :)  Does anyone think that this is an issue, or should we=20
ignore it?

Cheers,
Lachlan

On Fri, 24 Oct 2003 01:09, Neal Richter wrote:

> I would also encourage each of you to use valgrind to check for
> memory leaks while you are testing. Again, the depth you go looking
> for them is up to you.

--=20
lh...@us...
ht://Dig developer DownUnder  (http://www.htdig.org)