29 Dec
2006
29 Dec
'06
3:30 p.m.
Michael B. Brutman wrote:
Ok, it's broken! Testing is over for now ...
(The heap became corrupted sometime within the last hour. Time to start
reading traces.)
Thanks for all of the help. It wasn't as much traffic as I would have
liked, but it's broken just the same. :-)
Mike
And just for the record, the cause of the heap corruption was probably
me calling free twice on the same piece of allocated memory. I didn't
trace out the exact call flow that caused the problem, but I can see
where I could free the same buffer twice. And if you do that, TC++ 3.0
will report a corrupted heap.
I allocated the memory with malloc, not new, so C must be bad and C++ is
superior. ;-)
Mike