[KinoSearch] revision 3552 SEGV during indexing

[Marvin Humphrey]

OK, I think I may have squashed the bug.  I still haven't reproduced  
the problem, because that requires both an elaborate schema and luck  
in order of hash iteration.  However, I found an place that could  
cause an uninitialized value error.  Please try r3558.

On Jul 3, 2008, at 3:18 AM, Henry wrote:

> Thanks for the prompt reply.  Please find attached the results of  
> running
> valgrind with  "-v --leak-check=full".
>
> If you need me to rerun with different args, or change something,  
> please
> let me know.


In this case, we were just looking for errors, so the simple command  
would have sufficed.  But FYI, full checks look something like this:

   $ valgrind --leak-check=full --show-reachable=yes \
   > --suppressions=../devel/conf/p510_valgrind.supp \
   > /usr/local/debugperl/bin/perl510 -Mblib t/214-spec_field.t

I'm actually surprised that your report didn't show a bunch of known  
leaks related to boot up, which ordinarily have to be suppressed.   
Also, unless you're running a debugging perl, Perl usually leaks like  
crazy on shutdown because it just abandons everything rather than  
waste time on pointless one-by-one cleanup.

But whatever... the report showed me what I needed to see.

Marvin Humphrey
Rectangular Research
http://www.rectangular.com/


_______________________________________________
KinoSearch mailing list
KinoSearch at rectangular.com
http://www.rectangular.com/mailman/listinfo/kinosearch