> I've now made set_sec_vbits8 dump the tree before and after setting > the line and it looks very simple: > > 0xFEC7CD30 > 0xFEC7CD70 > --11681-- setting line 0x75D0EA0 > 0xFEC7CD30 > 0xFEC7CD70 > 0x75D0EA0 > > So we have a tree with 2 notes, insert a third and get an unordered tree > out.
Sheesh. That's very strange, because the AVL stuff has been intensively hammered on since it was installed, well over a year ago. Can you send your tree-check routine? I am curious to use it in mc_expensive_sanity_check to see if it shows the problem happening but undetected on any other programs. I had a brief check through m_oset.c, looking for word size and signedness issues to do with fast-case comparisons of keys (as is used here), but saw nothing suspicious. J ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Valgrind-developers mailing list Valgrind-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-developers
