Teach Yourself Borland C++ in 14 Days - portal

414 Day 11
Figure 11.9.
The Call stack
window.
NOTE
In this case the first function on the list is TMainForm::WatchBtnClick(). Following that you
see calls to some VCL functions and a couple calls to functions (unnamed) in the Windows
KERNEL32.DLL. Remember that the functions are listed in reverse order—the function
executed last shows up first in the call stack list.
Double-clicking on a function name in the Call stack window will take you to the source code
line for that function if the function is in your program. In case of functions in Windows
DLLs, the Call stack window will contain just an address and the name of the DLL. Doubleclicking
on a listed function that is contained in a DLL will display the CPU View window
(the CPU View is discussed in the next section).
If you have linked to the debug version of VCL, double-clicking on a
VCL method in the Call stack window will display the VCL source
code for that method. If you have not linked to the debug version of
VCL, double-clicking on a VCL method in the Call stack window will
display the CPU View.
Viewing the call stack is most useful after a Windows Access Violation error. By viewing the
call stack, you can see where your program was just before the error occurred. Knowing where
your program was just before it crashed is often the first step in determining what went wrong.
TIP
If the call stack list contains seemingly nonsensical information, it
could be that the call stack was corrupted. A corrupted call stack is
usually an indicator of a stack problem. This is not as likely to occur in
a 32-bit program as it is in a 16-bit program, but it can still happen.