Table of Contents
Advertisement
Chapter 3: Loading and Executing Programs
Using Breakpoints
Breakpoint address
The breakpoint address (ADDRESS) shows the memory location of the
breakpoint. The debugger displays the address as a hexadecimal value.
Module/function
The module/function field (MOD/FNCT) displays either the name of the
module containing the breakpoint or the name of a function if you qualified
the breakpoint with a function name. If you specify a module name with a
breakpoint command, the name must be followed by a line number (for
example: main\#80 ). The field width is eight characters. The debugger
truncates field entries greater than eight characters in length to eight
characters.
Line number
The line number entry (LINE) displays a module line number if you set a
breakpoint in a high-level module. If the compiler did not generate executable
code for the C statement at the line number specified, the debugger examines
the source code and sets a breakpoint on the next line number for which the
compiler generated executable code.
In the code window, the debugger places asterisks beside all line numbers that
are associated with breakpoints. The debugger places period symbols (.) beside
line numbers that are specified as breakpoints, but have no code associated
with them.
Breakpoint type
The breakpoint type (TYPE) describes what type of breakpoint is set:
instruction, read, write, or access. In assembly-level mode, the debugger sets
instruction breakpoints on microprocessor instruction addresses. In high-level
mode, the debugger sets instruction breakpoints on source line numbers. The
debugger flags instruction breakpoints with /A (assembly-level) or /H
(high-level). When switching between modes, these flags are useful for
differentiating between the different types of breakpoints.
Command argument
The debugger records arguments (COMMAND ARGUMENT) in the
breakpoint window as you entered them on the command line. Line numbers,
97
Advertisement
Table of Contents
