[Xapian-discuss] errors with flint database, xapian 1.0.4
Olly Betts
olly at survex.com
Thu Dec 6 10:56:34 GMT 2007
On Thu, Dec 06, 2007 at 12:20:11PM +0600, Vasiliy Sergeev wrote:
> I attach log-file from svn version checking.
Can you run:
cd tests
./runtest ./apitest -b flint -v zerodocid1 puncterms1 checkatleast3 valuerange1 sortrel1 adddoc4 emptyterm2
./runtest ./apitest -b multi -v zerodocid1 puncterms1 checkatleast3 valuerange1 sortrel1
> I doubt that problem is in valgrind incorrect reports.
Perhaps "incorrect" is the wrong word - the issue that Richard refers to
is that zlib deliberately performs multi-byte reads beyond the end of
the passed buffer in some cases. Technically this is wrong, but it's
actually safe in the cases where it does it, and it is done for
performance reasons.
Valgrind doesn't normally report this as it has suppressions for such
cases, but those included don't match the errors reported on some newer
64 bit platforms (Ubuntu gutsy on x86-64 for example)
> I also was unable
> to make a simple test on php5 after installing xapian-core and xapian
> php-binding.
> php simple code that add one document to created Db.
> <?php
> include "xapian.php";
> $_xapianDB = new XapianWritableDatabase("./database",
> Xapian::DB_CREATE_OR_OPEN);
> $xapianDoc = new XapianDocument();
> $xapianDoc->add_posting('1000',1);//, 100000);
> $_xapianDB->add_document($xapianDoc);
> ?>
So what does this actually do wrong?
Does "make check" on the php subdirectory of "xapian-bindings" report
any problems?
Cheers,
Olly
More information about the Xapian-discuss
mailing list