Displaying 3 results from an estimated 3 matches for "flinttabl".
Did you mean:
flinttable
2007 Jul 24
1
Xapian::DocNotFoundError on replace_document? (Called from Search::Xapian)
Hello,
I'm using Xapian 1.0.2 (flint) and matching Search::Xapian.
I'm getting:
terminate called after throwing an instance of
'Xapian::DocNotFoundError', which dumps core.
at first it was after adding my 2nd document (to an empty db, although
I don't know if that has any bearing) to the database with a
replace_document() call.
I shifted the first document off the
2010 Feb 01
0
Solaris core dump
...C. Users can run queries for a few hours
with no problems, then it returns "inflate failed (invalid code
lengths set)" to Python and dumps core. gdb reports:
#0 0xfe6dc910 in inflate_table () from /usr/lib/libz.so.1
#1 0xfe6d9d6c in inflate () from /usr/lib/libz.so.1
#2 0xfe2ebe20 in FlintTable::read_tag (this=0x75ed70, C_=0x75ede0,
tag=0xfdcf8568, keep_compressed=false)
at backends/flint/flint_table.cc:1254
#3 0xfe2eff70 in FlintTable::get_exact_entry (this=0x75ed70, key=@0xfdcf8578,
tag=@0xfdcf8568) at backends/flint/flint_table.cc:1190
#4 0xfe2ddc04 in FlintSpellingTable::o...
2010 Feb 01
2
Xapian core dumping on Solaris
...C. Users can run queries for a few hours
with no problems, then it returns "inflate failed (invalid code
lengths set)" to Python and dumps core. gdb reports:
#0 0xfe6dc910 in inflate_table () from /usr/lib/libz.so.1
#1 0xfe6d9d6c in inflate () from /usr/lib/libz.so.1
#2 0xfe2ebe20 in FlintTable::read_tag (this=0x75ed70, C_=0x75ede0,
tag=0xfdcf8568, keep_compressed=false)
at backends/flint/flint_table.cc:1254
#3 0xfe2eff70 in FlintTable::get_exact_entry (this=0x75ed70, key=@0xfdcf8578,
tag=@0xfdcf8568) at backends/flint/flint_table.cc:1190
#4 0xfe2ddc04 in FlintSpellingTable...