5.3.2. Setting simple conditional breakpoints

The Simple Breakpoints menu, shown in Figure 5.7, also enables you to set simple breakpoints quickly from the default Code window:

Set from Function/Label list...

Enables you to set a breakpoint on any number of the function names and labels in your image.

The Function Breakpoint/Profile Selector dialog box does not provide a record of breakpoints already set, that is, when you next open this dialog box existing breakpoints are not checked.

Simple Break if X...

Displays the dialog box, shown in Figure 5.11, enabling you to specify an expression that evaluates to an address.

Figure 5.11. Simple Break if X dialog box

Simple Break if X dialog box

The Breakpoint Type controls the type of memory, program, or data, and the type of access that stops execution. In this case, this shows SW Instr as the given type. This field is set to read-only where this is the only type of breakpoint supported by your debug target.

If your target supports hardware breakpoints, click on the drop-down arrow to display a list of the available types.

Simple Break if X, N times...

This option is similar to the previous option except that now you can specify how many times execution must arrive at the specified address before the breakpoint triggers. Select this option to display a dialog box where you can specify an address for a breakpoint, shown in Figure 5.12.

Figure 5.12. Simple Break if X, N times dialog box

Simple Break if X, N times dialog box

The additional field, After _ times, enables you to specify the number of times execution must arrive at the specified address to trigger the breakpoint, for example, when Proc_4 has been executed 150 times.

Note

If you are using a debug target that supports it, the pass count can be made in hardware.

Simple Break if X, when Y is True...

Displays a dialog box where you can specify an address for a breakpoint, shown in Figure 5.13.

Figure 5.13. Simple Break if X, when Y is True dialog box

Simple Break if X, when Y is True dialog box

The additional field, When expression is True, enables you to specify an expression (given in C format) that must be true when execution arrives at the specified address for the breakpoint to be triggered.

Named...

When working with a user-defined project or an auto-project, you can specify named, or standard, breakpoints that are saved in the project and so are available during your debugging session.

If enabled, click this option to select project-specific breakpoints from the predefined list, shown in Figure 5.14.

Figure 5.14. Named breakpoints list

Named breakpoints list

An item in the list that is grayed means that a symbol is specified for the breakpoint but this is not loaded.

The list of named breakpoints is maintained as part of the project SETTINGS group, see Specifying breakpoints for details of setting up these breakpoints.

Processor Events...

If supported by your debug target, RealView Debugger maintains a list of processor events that automatically trigger a breakpoint in any application program. During your debugging session you can examine this list and select, or deselect, halting events. Select this option to display a list selection box, shown in Figure 5.15.

Figure 5.15. Global Breakpoints list selection box

Global Breakpoints list selection box

The list box shows processor events that stop execution. An event is enabled when the associated check box contains a tick. Click on a check box to enable, or disable, a chosen event.

These are global breakpoints, that is they apply to processor events and not addresses.

Copyright © 2003, 2004 ARM Limited. All rights reserved.ARM DUI 0234B
Non-Confidential