Mike Shaver wrote:
> Crashes in the malloc()/free() code are almost always caused by
> double-freeing of a pointer, or freeing a pointer that wasn't allocated
> by malloc, in my experience.

Buffer overruns are also notorious for this. Also they can lay dormant
for several heap calls before the damage is noticed.

Reply via email to