RealView Debugger User Guide - ARM Information Center

Working with Breakpoints4.1 Breakpoints in RealView DebuggerBreakpoints are specified locations where execution must stop. The breakpoint can betriggered by:• execution reaching the specified address• data reads or writes at a specified address or address range• breakpoint qualifiers passing specified test criteria• data values at the specified location, in the current context, becoming equal to aparticular value or range.When a breakpoint triggers, RealView Debugger can carry out higher level requests. Forexample you can:• attach macros to breakpoints• output messages• update windows or files• change the behavior of your application program.You can also continue execution of your application program after RealView Debuggercompletes the specified operations.This section describes:• Breakpoint types• Qualifying breakpoint line number references with module names on page 4-7• Specifying address ranges on page 4-7• Specifying the entry point to a function on page 4-8• Breakpoints and memory map locations on page 4-9• Viewing breakpoints in your code view on page 4-10• Halted System Debug and Running System Debug on page 4-12• Using hardware breakpoints on page 4-13• Breakpoints and image restarts on page 4-14• Using breakpoints with RealView ICE on page 4-14.4.1.1 Breakpoint typesRealView Debugger enables you to use different types of breakpoint when you aredebugging your image, described in:• Software and hardware breakpoints on page 4-3• Unconditional and conditional breakpoints on page 4-4• Default breakpoints in the GUI on page 4-54-2 Copyright © 2002-2005 ARM Limited. All rights reserved. ARM DUI 0153G