Skip navigation.
 
mlRe: Isolating a bug?
FROM : M. Uli Kusterer
DATE : Wed Apr 06 13:37:02 2005

At 6:46 Uhr -0400 06.04.2005, Gregory Weston wrote:
>From a program that's been shipping for about a year now without
>stability complaints, I user sent a crash log that I find vexing.
>Why? Because here's the call stack.


That bug looks suspiciously like you're stomping memory somewhere.
Often this is when you're releasing an object that you don't own but
access it later on. This will often work fine several times because
the memory hasn't been reused and thus still contains the data from
the previous (valid) object, and then suddenly part of it gets
re-used and everything goes bang, either in your object, or in the
object that got the re-used space assigned, because you changed it
through a call to your released object.
--
Cheers,
M. Uli Kusterer
------------------------------------------------------------
        "The Witnesses of TeachText are everywhere..."
                    http://www.zathras.de

Related mailsAuthorDate
mlIsolating a bug? Gregory Weston Apr 6, 12:46
mlRe: Isolating a bug? <java_nutt Apr 6, 13:03
mlRe: Isolating a bug? M. Uli Kusterer Apr 6, 13:37
mlRe: Isolating a bug? Ondra Cada Apr 6, 13:41
mlRe: Isolating a bug? Angela Brett Apr 6, 13:42
mlRe: Isolating a bug? Jonathon Mah Apr 6, 14:02
mlRe: Isolating a bug? Gregory Weston Apr 6, 15:54
mlEnable Guard Malloc (was Re: Isolating a bug?) daniel Apr 6, 18:31
mlRe: Enable Guard Malloc (was Re: Isolating a bug?) daniel Apr 6, 18:47