From: qballlives AT aol DOT com (QBallLives)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: 'Call Frame TraceBack'  Plz help a rookie !
Date: 24 Jan 1998 12:51:21 GMT
Lines: 35
Message-ID: <19980124125101.HAA29740@ladder01.news.aol.com>
NNTP-Posting-Host: ladder01.news.aol.com
Organization: AOL http://www.aol.com
References: <34C550C2 DOT 38B1 AT elv DOT enic DOT fr>
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

>Hi
>Please, excuse my stupid question (and my english), but i've a pbm under 
>Rhide v1.4 and djgpp 2.0 with a c++ program.
>
>When compiling, no problem, but at running time, I always get the same 
>message : Call Frame Traceback from Rhide.
>
>Can you help me ?
>Plz, answer by mail if possible
>chafer AT elv DOT enic DOT fr
>
>Thanks ;)
>
>Camille Chafer      France
>
>

Ok Frenchie... I'll give it a shot...

Call Frame Tracebacks... as far as I know so far... happen when you do things
like divide by 0.... or try to memcpy 0 bytes

... trying to do things w/ memory that hasn't been allocated... stuff like
that...

Using RHIDE... you should be able to pin-point WHERE the problem occured... by
clicking on the "Call Frame Traceback" text... (sometimes it can be a little
stubborn... )

post the module you trace the error back to.... and highlight the line... I'm
sure alot of people will be willing to help..

Jim the loiterer
aloiterer AT juno DOT com
http://members.xoom.com/JimMcCue/index.htm