At 12:42 AM -0700 7/30/02, Lo Saeteurn wrote:
Basically, it lets you know where the error occurred, but don't care about
the crash shortly afterward.
But that's the whole point. A failed assertion may occur at a point
that's quite remote from the actual cause of the problem. Some code
may scribble on memory and cause some kind of malfunction much later
that shows a Failed Assertion. A failed assertion means that
something that should be impossible happened anyway. That means that
the program isn't behaving logically and thus the failed assertion
may have nothing what so ever to do with the real cause of the
problem.
Regards,
Joe Huber
|