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

[Marvin Humphrey]

On Jun 27, 2008, at 2:01 AM, Edward Betts wrote:

>
> The data to be indexed is being read from a pipe, but there are no
> threads involved.


Could we be seeing an out-of-memory error?  KS doesn't wrap malloc  
calls to verify that NULL wasn't returned.  (It should probably  
start.)  That would explain at least one of the errors, and possibly  
the other if in fact it was the assignment to the newly allocated  
"self" that failed rather than the refcount increment:

24              self->_ = REFCOUNT_INC(vtable);

Do you see memory growing out of control?  I can see at least a couple  
leaks as the valgrind tests progress.

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


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