Greetings all, Thanks, Neal, for your work setting up the tasks!
When I run valgrind, I get ==4058== Conditional jump or move depends on uninitialised value(s) ==4058== 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 forgettable :) Does anyone think that this is an issue, or should we 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. -- [EMAIL PROTECTED] ht://Dig developer DownUnder (http://www.htdig.org) ------------------------------------------------------- This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/ _______________________________________________ ht://Dig Developer mailing list: [EMAIL PROTECTED] List information (subscribe/unsubscribe, etc.) https://lists.sourceforge.net/lists/listinfo/htdig-dev
