From: "Hazel Moore" Newsgroups: comp.os.msdos.djgpp Subject: Re: Seemingly random callframe tracebacks Date: Thu, 14 Dec 2000 16:56:11 -0800 Organization: Posted via Supernews, http://www.supernews.com Message-ID: References: X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 X-Complaints-To: newsabuse AT supernews DOT com Lines: 22 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Alright, I checked out the huge FAQ at delorie.djgpp.com. I never knew all that stuff was there! Thanks for the direction! "Eli Zaretskii" wrote in message news:Pine DOT SUN DOT 3 DOT 91 DOT 1001214115719 DOT 25353U AT is... > > 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.