Teach Yourself Borland C++ in 14 Days - portal

398 Day 11
As you step through the program, the execution point is highlighted in blue and the editor
window gutter displays a black arrow glyph. Understand that the line highlighted in blue has
not yet been executed but will be executed when program execution resumes.
Once you have stopped at a breakpoint, you can view variables, view the call stack, browse
symbols, or step through your code. After you have inspected any variables and objects, you
can resume normal program execution by clicking the Run button. Your application will
again run normally until the next breakpoint is encountered.
NOTE
It’s common to detect coding errors in your program after you have
stopped at a breakpoint. If you change your source code in the middle
of a debugging session and then choose Run to resume program
execution, the IDE will prompt you with a message box asking whether
you want to rebuild the source code. If you choose Yes, the current
process will be terminated, the source code will be recompiled, and the
program will be restarted.
The problem with this approach is that your program does not get a
chance to close normally, and any resources currently in use might not
be freed properly, which could result in memory leaks. While Windows
95 and Windows NT handle resource leaks better than 16-bit Windows,
it is still advisable to terminate the program normally and then
recompile.
The Breakpoint List Window
The C++Builder IDE keeps track of the breakpoints you have set in the Breakpoint list
window. To view the breakpoint list, choose View | Breakpoints from the main menu. The
Breakpoint list window will be displayed, as shown in Figure 11.2.
Figure 11.2.
The Breakpoint list
window.
The Breakpoint list window has four columns. The first column, Filename, shows the
filename of the source code unit in which the breakpoint is set. The second column, labeled
Line, shows the line number on which the breakpoint is set. The Condition column shows