[Xapian-discuss] Future of Xapian (long)

Olly Betts olly@survex.com
Mon, 21 Jun 2004 22:18:33 +0100


On Mon, Jun 21, 2004 at 10:28:20AM +0100, Richard Boulton wrote:
> I ran the threaded tests Eric supplied using helgrind to check for data 
> races, and got several reports of problems in the std::string stuff.  Of 
> course, helgrind does have a tendency to report false positives, so I 
> thought I'd check if I still got the reports when using a different STL 
> implementation.

Another thing to try is telling the GCC STL not to pool memory.  The
valgrind FAQ entry 4.3 has some info:

http://valgrind.kde.org/faq.html

Essentially if you're using GCC 3.2.2 or later, try exporting
GLIBCPP_FORCE_NEW before running the test program.

Also, if you're using CVS HEAD, update to the latest.  If you're using
0.8.0, apply the two patches I pointed Eric to recently.

Cheers,
    Olly