Date: Mon, 22 Nov 1999 20:05:10 -0500
Message-Id: <199911230105.UAA19498@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: djgpp AT delorie DOT com
In-reply-to: <81cjle$l3f$1@news-hrz.uni-duisburg.de> (MephistoI@gmx.net)
Subject: Re: Debugger Error
References:  <81cjle$l3f$1 AT news-hrz DOT uni-duisburg DOT de>
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


>     "Call Frame Traceback".

When one function calls another function, it sets aside part of the
stack for its local variables and such.  It uses a linked list to link
them together, and uses a register to point to it's own area.  This
area is the "stack frame" for that function.  At any given time, you
can scan the linked list and see all the currently pending function
calls.  If you list them back from the first one (the current
function), it traces back through the function calls and shows you how
you got to where you are from main().  That's a call frame traceback.

Why the debugger is giving it to you is a different problem, but it
often tells you where the program "was" when it crashed.