[KinoSearch] QueryFilter Crashings and Smashings

[Marvin Humphrey]

On Jun 1, 2007, at 1:42 PM, Marvin Humphrey wrote:

> I suspect that the problem will be found within ANDScorer_skip_to().

OK, I took a shot at this and couldn't find any flaws in the  
ANDScorer_skip_to algo.  I'll need more info.

(You haven't changed up any of the field defs, have you?)

Please update to the latest repository revision -- the error messages  
in InStream were using a 64-bit integer that Perl's sv_catpvf  
couldn't handle, and "start: 0" is probably wrong.

   Error in function refill at ../c_src/KinoSearch/Store/InStream.c: 
92: Read
   past EOF of _1.p1 (start: 0 len 912) at
   /usr/local/lib/perl5/site_perl/5.8.4/darwin-2level/KinoSearch/ 
Searcher.pm
   line 122

_1.p1 is a postings file for field number 1 in segment _1.  I'd like  
to know what the file length is for _1.p1, and what field corresponds  
to field 1 in segment _1.  All that information can be found in the  
latest segments_XXX.yaml file.  If there's no proprietary info in the  
segments file, please consider pasting its contents into an email so  
we can examine it.

It would be useful to know if it's the same field at the same spot  
erroring out over and over or if the locus changes.

The only thing which could be reading the _1.p1 file is a TermScorer  
subclass in the midst of scoring.  We need to know exactly what  
aspect of scoring is triggering the glitch.  Unfortunately, the stack  
traces yielded by the CONFESS macro only contain the Perl call stack,  
not the C stack -- so we have to go hunting.

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