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

[Marvin Humphrey]

On Jun 27, 2008, at 1:04 AM, Edward Betts wrote:

> [Switching to Thread -1210591040 (LWP 27080)]

This isn't a multi-threaded application, is it?  (KS isn't thread- 
safe.)  I don't immediately see anything else out of the ordinary in  
either of the two backtraces.

The first crash happened when manipulating a refcount on a compile- 
time-created vtable object which is supposed to be immortal.  The  
other occurred in a completely different place, when zeroing out some  
newly allocated memory after extending an array.  There's seemingly no  
pattern.  Maybe it's the delayed effect of earlier memory corruption.   
I'll set the valgrind tests running and see if anything turns up.

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


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