On Sat, Nov 06, 2010 at 05:42:27PM +0100, Jan Schulz wrote: > linus:/home/jan# gdb --args python /usr/sbin/update-apt-xapian-index > --update --quiet [...] > (gdb) where > #0 0xb750d515 in __cxa_throw () from /usr/lib/libstdc++.so.6 > #1 0xb74a3eef in std::__throw_length_error(char const*) () > from /usr/lib/libstdc++.so.6 > #2 0xb74e9d82 in std::basic_string<char, std::char_traits<char>, > std::allocator<char> >::assign(char const*, unsigned int) () from > /usr/lib/libstdc++.so.6 > #3 0xb7622f7b in FlintCursor::get_key(std::basic_string<char, > std::char_traits<char>, std::allocator<char> >*) const () from > /usr/lib/libxapian.so.22 > #4 0xb7623c7f in FlintCursor::next() () from /usr/lib/libxapian.so.22 [...] > Hope you can do something with this, I've no idea whats happening here :-)
I've asked the Xapian authors who suspect a corrupted database. It's quite strange because apt-xapian-index' cronjob should do a full rebuild once a week. You can try manually running "update-apt-xapian-index --force" to force a full rebuild, maybe? Ciao, Enrico -- GPG key: 4096R/E7AD5568 2009-05-08 Enrico Zini <enr...@enricozini.org>
signature.asc
Description: Digital signature
