
To break on an access to a variable
If you started the debugger using the Startall script, skip this section. Access
breakpoints are disabled because the analyzer has been configured to use the
Trig2 trigger for other purposes.
You can also set breakpoints on a read, a write, or any access of a variable.
This helps to locate defects due to multiple functions accessing the same
variable. Suppose you want to break on the access of the variable num_checks.
("&num_checks" should still be in the entry buffer.)
1 Set the breakpoint by selecting Breakpoints
→
Set
→
Read/Write () .
2 R un the program by clicking on the Run action key.
When the program stops, the code window shows that the program stopped at
the next reference to the variable num_checks. Due to the latency of the
emulation analyzer, the processor may halt up to two instruction cycles after
the breakpoint has been detected.
Try running the program a few more times to see where it stops. (Notice that
num_checks is passed by reference to interrupt_sim. Since counter points to the
same address as num_checks, the debugger stops at references to counter.)
3 Delete the access breakpoint. Select Window
→
Breakpoints, place the mouse
in the Breakpoint window, press and hold the right mouse button, and choose
Delete All Breakpoints.
Chapter 1: Getting Started with the Graphical Interface
To break on an access to a variable
31
Summary of Contents for B1476 68020
Page 1: ...User s Guide HP B1476 68020 030 Debugger Emulator ...
Page 25: ...Part 1 Quick Start Guide ...
Page 26: ...Part 1 2 ...
Page 39: ......
Page 76: ...Chapter 2 Getting Started with the Standard Interface To end the debugging session 52 ...
Page 77: ...Part 2 User s Guide ...
Page 78: ...Part 2 54 ...
Page 112: ...Chapter 3 Entering Debugger Commands Viewing Debugger Status 88 ...
Page 152: ...Chapter 4 Loading and Executing Programs Using the Debugger with the Branch Validator 128 ...
Page 153: ...5 Viewing Code and Data How to find and display source code and memory contents 129 ...
Page 206: ...Chapter 5 Viewing Code and Data If problems occur when using simulated I O 182 ...
Page 230: ...Chapter 6 Making Trace Measurements If tracing is not triggered as expected 206 ...
Page 270: ...Chapter 8 Using Macros and Command Files Using Command Files 246 ...
Page 307: ...10 Configuring the Emulator How to configure the emulator for your target system 283 ...
Page 321: ......
Page 353: ...Part 3 Concept Guide ...
Page 354: ...Part 3 330 ...
Page 355: ...11 X Resources and the Graphical Interface An introduction to X resources 331 ...
Page 368: ...Chapter 11 X Resources and the Graphical Interface 344 ...
Page 369: ...Part 4 Reference ...
Page 370: ...Part 4 346 ...
Page 371: ...12 Debugger Commands Detailed descriptions of command line commands 347 ...
Page 524: ...Trace Trigger Chapter 12 Trace Trigger 500 ...
Page 574: ...Chapter 13 Expressions and Symbols in Debugger Commands Symbolic Referencing 550 ...
Page 575: ...14 Reserved Symbols 551 ...
Page 579: ...15 Predefined Macros 555 ...
Page 616: ...Chapter 15 Predefined Macros write 592 ...
Page 617: ...16 Debugger Error Messages A list of the error messages generated by the debugger 593 ...
Page 638: ...Chapter 17 Debugger Versions 614 ...
Page 639: ...Part 5 Installation Guide ...
Page 640: ...Part 5 616 ...
Page 641: ...18 Installation How to install the debugger software on your computer 617 ...
Page 671: ...Chapter 18 Installation Configuring Terminals for Use with the Debugger 647 ...
Page 722: ...Index 698 ...