Comment 9 for bug 956775

Ok, this is written in linux malloc manpage:

Crashes in malloc(), calloc(), realloc(), or free() are almost always related to heap corruption, such as overflowing an allocated chunk or freeing the same pointer twice.

Ildar, what OS do you have? Also please run startool under valgrind. It will print all memory corruptions.

And can somebody other reproduce this bug?