wdbgbrkp.gml

开放源码的编译器open watcom 1.6.0版的源代码

.*
.menuitem Save
.*
.ix 'breakpoint' 'saving'
Save all breakpoint information to a file. This is useful when you are
creating complicated breakpoints. You can save and restore them in a
later debugging session.
.*
.menuitem Restore
.*
.ix 'breakpoint' 'restoring'
Restore a set of breakpoints that were saved by using
.menuref 'Save' 'Break'
.dot
.*
.endmenu
.*
.section *refid=wndbrk The Break Window
.*
.ix 'breakpoint' 'window'
.figure *depth='2.50' *scale=65 *file='dbgbrk' The Break Window
.np
The
.wnddef Break
window displays each breakpoint and its status. It appears when you
select the
.menuref 'View All' 'Break'
A breakpoint button appears at the left of each line. You can click on
this button to enable and disable a breakpoint. Unlike the source and
assembly windows, the button will not clear the breakpoint. Next
appears the address of the breakpoint. Finally, for break-on-execute
breakpoints, the source or assembly code at the break point location
is displayed. For break-on-write breakpoints, the current value of the
location is displayed in hex.
.np
You can modify any break point by double clicking on it, or by
cursoring to it and pressing enter. The Breakpoint Options dialog will
appear to allow you to modify the break point. Press the right mouse
button to access the following pop-up menu items:
.*
.begmenu Break Pop-up
.*
.menuitem Modify
.*
.ix 'breakpoint' 'changing'
Change the definition of the selected breakpoint. The Breakpoint dialog
will appear.
.*
.menuitem New
.*
.ix 'breakpoint' 'creating new'
Add a new breakpoint. An empty Breakpoint dialog will appear. You must
specify the address of the new Breakpoint. Refer to the section
entitled :HDREF refid='dlgbrk'. for a description of the items in the
which appear in the dialog.
.*
.menuitem Delete
.*
.ix 'breakpoint' 'deleting'
Delete the selected breakpoint.
.*
.menuitem Enable
.*
.ix 'breakpoint' 'enabling'
Enable the selected breakpoint.
.*
.menuitem Disable
.*
.ix 'breakpoint' 'disabling'
Disable the selected breakpoint.
.*
.menuitem Source
.*
.ix 'breakpoint' 'finding source code'
Display the source code associated with the break point. This
operation only makes sense for break-on-execute breakpoints.
.*
.menuitem Assembly
.*
.ix 'breakpoint' 'finding assembly code'
Display the assembly code associated with the selected line. This
operation only makes sense for break-on-execute breakpoints.
.*
.endmenu
.*
.section *refid=dlgbrk The Breakpoint Dialog
.*
.figure *depth='3.70' *scale=70 *file='dlgbrk' The Breakpoint Dialog
.np
The breakpoint dialog appears when you select
.menuref 'At Cursor' 'Break'
or
.menuref 'New' 'Break'
and whenever you attempt to modify a break point. It allows you to
define the breakpoint and set all of its conditions. A description of
the items in the dialog follows.
.begnote $break
.note Address
.ix 'breakpoint' 'specifying address'
This edit field displays the address tag associated with the selected
breakpoint.
.np
When you choose
.mi At Cursor
this field already contains an address that describes the line of code
that the cursor is on. The format of the address tag is
.monoon
symbol+offset
.monooff
where
.monoon
symbol
.monooff
is the name of the nearest function and
.monoon
offset
.monooff
is distance in bytes past that symbol where the break point is
defined. It is normally best NOT to edit this field. To change the
line of source code, leave the dialog, move the cursor to where you
want the breakpoint, and use the
.mi At Cursor
command again.
.np
When you choose
.mi New
.ct ,
this field is empty. You can type any valid address expression in this
field. It can be the name of a function, global variable. Refer to the
section entitled :HDREF refid='videxpr'. for more information about
address expressions.
:INCLUDE file='symbuttn.gml'.
.begnote
.note Note:
Be careful when using local (stack) variables for a break-on-write
breakpoint. As soon as execution leaves the scope of the variable, the
memory will change at random since the variable does not really exist
any more and the memory will be used for other variables. Also, if
execution enters that variable's scope again, the variable may not
have the same memory address.
.endnote
.note Condition
.ix 'breakpoint' 'condition'
Use this field to enter a conditions that must be met before a
breakpoint will trigger. The condition can be an arbitrary debugger
expression. These include statements in the language you are
debugging. A valid example for the C language is
.monoon
i == 1.
.monooff
.note Break on Execute
.ix 'breakpoint' 'on execute'
Check this field to create a break-on-execute breakpoints. If you
choose Execute, be sure that the address field contains a code address
(function name or code line number) and not a variable address.
Variable are never executed. If the address field names a variable,
the breakpoint will never trigger.
.note Break on 1 Byte/2 Bytes/4 Bytes...
.ix 'breakpoint' 'on write'
Check one of these fields to create break-on-write breakpoints. If you
choose one of these options, be sure that the Address field contains a
variable address and not a code address. A code address will never be
written to, so the breakpoint will never trigger. The size of the
memory location is defined by the checkbox you use as follows:
.begnote $compact
.note 1 Byte
The breakpoint will trigger only when the first byte
of the memory address is written to.
.note 2 Bytes
The breakpoint will trigger when either of the first two bytes
at the memory address are written to.
.note 4 Bytes
The breakpoint will trigger if any of the first four bytes
of the memory address are written to.
.note etc.
The breakpoint will trigger if any of the first "n" bytes
of the memory address are written to.
.endnote
.note Countdown
.ix 'breakpoint' 'countdown'
Use this field to enter the number of times an address must be hit
before the breakpoint triggers. Every time the breakpoint conditions
are met, the countdown decreases by one. The breakpoint will trigger
only after the countdown is at zero. Once the countdown reaches zero,
the breakpoint will trigger each time the conditions are met. If you
have also set a condition, the countdown will only decrease by one
when the condition is true.
.note Total Hits
.ix 'breakpoint' 'counting'
This field displays the total number of times an address has been hit.
This includes the times the breakpoint does not trigger because a
condition failed or the countdown has not yet hit zero.
.note Reset
Click on this button to reset the Total Hits field to zero.
.note Execute when Hit
.ix 'breakpoint' 'executing debugger commands'
Use this field to enter a debugger command. When the breakpoint is
triggered, the debugger will execute this command. You can use this
field to execute arbitrary C statements, change a variable or
register, or even set other breakpoints. For a more detailed
description of commands that can be entered in this field, refer to
the section called :HDREF refid='vidcmd'.. If you want to use this
field to execute a statement in the language you are debugging, you
need to use a DO command in front of the statement. For example, you
could enter
.monoon
DO i = 10
.monooff
to have the value of 10 assigned to i each time the breakpoint
triggered.
.note Resume
Check this field if you want the program to resume execution after the
.us Execute when Hit
command has been completed. This capability can be used to patch your
code.
.note Enabled
.ix 'breakpoint' 'status'
This field displays the current status of the breakpoint. If it is
checked, the breakpoint is enabled. If it is unchecked, the breakpoint
is disabled.
.note Value
For Break-on-Execute breakpoints this field displays the source line
or the assembly line at which the break point is defined.
For Break-on-Write breakpoints, this field displays the memory
contents.
.note Clear
.ix 'breakpoint' 'deleting'
Click on the clear button to clear the breakpoint and close the
dialog.
.endnote