Date: Thu, 14 Dec 2000 11:58:17 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Hazel Moore <dkmoore2 AT dragonbbs DOT com>
cc: djgpp AT delorie DOT com
Subject: Re: Seemingly random callframe tracebacks
In-Reply-To: <t3fqv467t7lke4@corp.supernews.com>
Message-ID: <Pine.SUN.3.91.1001214115719.25353U@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Wed, 13 Dec 2000, Hazel Moore wrote:

> For some reason, my program only works at random. Sometimes it works
> perfectly, some times it generates a callframe traceback, sometimes it
> simply displays nothing. But I have no random numbers being generated, it's
> the same code every time I run it. It gets most CFTB's (callframe
> traceback's) on masked_blits() or when I dynamically allocate memory with
> new, but it's never consistent!  Anybody know what causes this type of
> behavior?

It's usually a sign of using uninitialized memory.

Try reading section 12.2 in the FAQ, it might help you.