On Dec 7, 2007 3:01 PM, Tom Hughes <[EMAIL PROTECTED]> wrote: > It seems that the problem is that the AVL tree is getting out of > order. I made get_sec_vbits8 walk the oset when it detects the problem > and dump the addresses to the log and this is what I get: > > 0x28D448D0 > 0x28D44950 > ... > 0x28E81BF0 > 0x28E8C910 > 0x7F22ECE0 > 0x7F22ED30 > ... > 0x7F22F930 > 0x7F22F960 > 0xFEDD6D30 > 0xFEDD6D70 > 0x75D0EA0 > > At that point it stopped as it noticed the address going backwards.
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. Somehow VG_(OSetGen_Lookup) still works at that point though... Tom -- Tom Hughes ([EMAIL PROTECTED]) http://www.compton.nu/ ------------------------------------------------------------------------- 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
