17 Jun
2004
17 Jun
'04
9:11 a.m.
Pete wrote:
John, beware that my sample was only indicative of the problem associated with the stack trace I submitted along with it. A fact is that the "crash-point" is somewhere else each time. I have not paid sufficient attention to whether or not each crash involves heap allocation/deallocation activities. I will pay extra attention in future crashes though.
I'd suspect that you've written past the end of an allocated block of memory. If you do that then your program will crash next time you try to malloc() or free() memory. valgrind should find it for you (And lots and lots of other bugs :)