Debug Manual

Debug Commands
Debug Manual—421921-003
4-13
Set Trace Code Breakpoint
Examples
106,03,00040-B 100 + 117, L + 14 > 500
106,03,00040-B UC.2, 526, L+3 = 0
106,03,00040-B C, 2I, R4 <> 1
106,03,00040-B UL.1, 325, L+5 > 3
248,00,00045-B N 0x70450F1C, $T2 & 0xF000FFFF < 0x17
! Break in RISC code if the 32-bit value in $T2 logically
! ANDed with the mask value is less than 0x17.
Examples of Setting Conditional Code Breakpoints
The address where the breakpoint is located is determined in the same manner as
previously described in Set Unconditional Code Breakpoint on page 4-7. For examples,
see Appendix F, Sample Debug Sessions.
Set Trace Code Breakpoint
The B command can set a trace code breakpoint. A trace code breakpoint causes
Debug to list the contents of one or more registers or memory locations each time the
breakpoint location is executed. The trace form of the B command is:
address
is the code address where the breakpoint is to occur. For more information, see
Address Syntax on page 3-12. The address mode must follow the same guidelines
as those stated earlier in this section for specifying the code address when setting
an unconditional code breakpoint. The address parameter is limited to code
locations only.
register
is a processor register. For more information, see Register Syntax on page 3-7.
For a TNS process, when registers R0 through R7 are specified, the values in the
registers are evaluated when the breakpoint is executed. Other registers are
evaluated to a memory location pointed by the registers when the breakpoint is
executed.
For a TNS/R process, any register except the floating-point registers can be used.
start-address
is the address of the first variable to be listed. The syntax for start-address is
the same as the Address Syntax on page 3-12, but it is limited to only data
B address {, {register | start-address} ? count [, ALL ] }
{ [, ALL ], {register | start-address} ? count }