12.11. Example of breakpoint behavior

You can control the behavior of a breakpoint by assigning one or more condition qualifiers and actions to that breakpoint. The order that you add the condition qualifiers and actions determines the order they are processed by RealView Debugger. However, actions are performed only when the result of all specified condition qualifiers is True, even if you specify any actions before a condition qualifier.

To demonstrate the breakpoint behavior using the Dhrystone image:

  1. Connect to your debug target.

  2. Load the dhystone.axf image.

  3. Set a software breakpoint in dhry_1.c, at column 2 of line 153.

    Although you can use the RealView Debugger GUI to set breakpoints, it is easier to understand the interaction of qualifiers and actions using CLI commands.

    Enter the following CLI command:

    breakinstruction,qualifiers \DHRY_1\#153:0

    For qualifiers use the following (see the command qualifiers in Table 12.1, for each command qualifier variation):

    • A macro condition qualifier that specifies a macro to view a symbol, for example:

      define /R int viewSymbol()
        $printsymbol DHRY_1\clock_t$;
        return (0); //   0 - stop execution at the breakpoint
                    // >=1 - continue execution
    • A pass count condition qualifier that specifies five passes before the breakpoint is to be activated.

    • An action qualifier that prints the message Actions performed.

  4. Run the image, enter 10 when prompted for the number of runs.

  5. If you are using the RealView Debugger GUI, click the Cmd tab in the Output view to view the results.

  6. Repeat steps 3 to 6 for each command qualifier variation, and change the macro return value as indicated.

See also:

Copyright © 2002-2011 ARM. All rights reserved.ARM DUI 0153N