Hi, Yep, a loop in malloc_consolidate is normally a double free. MALLOC_CHECK_=2 should cause gdb to catch the double free where it happens also. Thanks for the backtraces, should be pretty easy to fix. Havoc