Tornado

7
Debugger
Then select the breakpoint type from the Breakpoint Type list, and click the
OK button.
To delete a breakpoint, click on its name in the Hardware Breakpoints
window, and then the Delete button. You can only delete hardware
breakpoints set during the current CrossWind session.
If the target agent is running in task mode, a hardware breakpoint is set on
all the system tasks. If the agent is running in system mode, a hardware
breakpoint is set on the system context.
NOTE: CrossWind does not manage hardware breakpoints in the same manner as
standard GDB breakpoints. The hardware breakpoint interface is provided as a
simple means of setting hardware breakpoints on the target (which is why it is only
possible to set hardware breakpoints on all the tasks or on the system context, and
not only on the task to which the debugger is attached).
7
When a data access hardware breakpoint stops the program, the context icon
indicates the line of code that has been executed. However, on some processors
(such as the I960), a data access exception is generated only after the data has been
accessed and the program counter has been incremented. For those processors,
CrossWind marks the line after the one that has been executed when data
hardware breakpoint was hit.
Interrupt. Sends an interrupt to the task that the debugger is controlling.
For example, if your program keeps running instead of following an
expected path to a breakpoint, press this button to regain control and
investigate. Pressing this button is equivalent to keying the interrupt
character (usually CTRL+C).
Steps to the next line of code. The precise effect depends on the style of
program display you have selected. If the program-display area shows
high-level source code only (the default), this button advances execution
to the next line of source, like the step command. On the other hand, if the
program-display panel shows assembler instructions (when either
Assembly or Mixed selected from the Source menu, or execution is in a
routine compiled with no debugging symbols), this button advances
execution to the next instruction—the equivalent of the stepi or si
command.
Steps over a function call. This is a variant of the button: instead of
stepping to the very next statement executed (which, in the case of a
function call, is typically not the next statement displayed), this button
steps to the next line on the screen. If there is no intervening function call,
247