5.2.3. Viewing breakpoints in your code view

Breakpoints are marked in the source-level and disassembly-level view at the left side of the window using color-coded discs:


This symbol shows the position of an enabled breakpoint. A second breakpoint cannot be set at the same location as an existing breakpoint.


If you set a conditional breakpoint, that is one that stops execution when certain conditions are met, the marker is a disc filled with yellow.


Where a breakpoint has been set previously and then disabled, it is marked by a white disc. If the breakpoint is re-enabled the disc changes color as appropriate for the type of breakpoint.

If you have set multiple breakpoint units, for example on a source line containing multiple statements or on inlined functions, then disabling the first breakpoint unit changes the marker disc, shown in Figure 5.6. If you disable the second breakpoint unit on the line, the marker remains.

Figure 5.6. Working with breakpoint units

Working with breakpoint units

See Using the Break/Tracepoints pane for details on viewing breakpoints in the Break/Tracepoints pane.

If you try to set a breakpoint on a non-executable line, RealView Debugger looks for the first executable line immediately following and places the breakpoint there. If the lines preceding the breakpointed instruction are comments, declarations, or other non-executable code, they are marked with black, downward pointing arrows. Lines marked in this way are regarded as part of the breakpoint. You cannot place two unconditional breakpoints on the same line, or on lines marked by the downward pointing arrows.

Thread-specific breakpoints are shown as green stop signs. See Chapter 19 RTOS Support for details of using these features.

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