>It still crashes, but in a less evident way. I therefore >ran it under valgrind, which complains a lot (but does >not crash). It looks like the code refers to memory that >has been freed already.
I'm not doing difficult memory things.. So i'm a bit puzzled. Is this also caused by the stdlib-debug thingies ? >PS: I am very impressed by this new compare feature. Even though it doesn't work for you ? Vincent
