Mar 25, 2009 at 4:42am Mar 25, 2009 at 4:42am UTC
I'm getting what seems to be a somewhat common error, that my heap has been corrupted. Unfortunately, I'm getting this on calling a new, which I assume means the issue occurs some time before this.
What can cause heap corruption?
Mar 25, 2009 at 12:21pm Mar 25, 2009 at 12:21pm UTC
Memory stomps, attempting to free memory that is not on the heap, double-freeing heap memory, etc...
Mar 26, 2009 at 2:11pm Mar 26, 2009 at 2:11pm UTC
>>double-freeing heap memory
jsmith:
I thought it was safe to delete a deleted pointer
Mar 26, 2009 at 6:14pm Mar 26, 2009 at 6:14pm UTC
But it is safe to delete 0. However, setting deleted pointers to 0 will not solve the real problem.
Mar 27, 2009 at 4:07am Mar 27, 2009 at 4:07am UTC
why dont you post your code so that somecan can find the error in it??