[KinoSearch] Re: Backtrace of segfault when building inverted index

Peter Karman peter at peknet.com
Sat Jun 28 06:13:03 PDT 2008



Marvin Humphrey wrote on 6/27/08 5:04 PM:
> 
> On Jun 27, 2008, at 2:52 PM, Edward Betts wrote:
> 
>> Thanks, the index finished without running out of memory.
> 
> 
> Groovy.  :)
> 
> Memory leakage has been a recurring, systemic problem for svn trunk 
> users like yourself, because the ordinary test suite doesn't catch such 
> problems and refcounting errors are so easy to make.  Since the last 
> discussion on this topic, I've been introduced to the CPAN module 
> Test::Valgrind.  Hopefully we can use that to set up a systemic 
> solution: nightly automated smokes.
> 

How timely. The last few nights I've been poking at the smoke test script I 
posted here several months ago, and think I've got it to a useable place. I just 
committed it to trunk as r3552.

I also read the pod for Test::Valgrind. I *think* smoke.pl could be altered to 
use it conditionally when it is installed. I committed smoke.pl so others can 
play with that idea too.

-- 
Peter Karman  .  http://peknet.com/  .  peter at peknet.com



More information about the kinosearch mailing list