only one breakpoint can be set?

[hg-chen]

Posted on August 18, 2008 at 11:21

only one breakpoint can be set?

[hg-chen]

Posted on May 17, 2011 at 09:54

This question should be related to IAR EWARM,

but I do not know the place of the IAR forum, using STR9 the question is while enter debugging, the message below shown, or refer to attached file. The C-SPY option ''Run to 'main''' is enabled,but due to a lack of breakpoints this will require single-stepping ,which may take a long time. Do you want to execute anyway,or stop at the first instruction? only one breakpoint can be set under this condition! why and how to get it right?

[jilisegiar]

Posted on May 17, 2011 at 09:54

Hi,

From EWARM user guide: nullBreakpoint consumersThere are several consumers of breakpoints in a debugger system. User breakpoints�?the breakpoints you define by using the Breakpoints dialog box or by toggling breakpoints in the editor window�?often consume one low-level breakpoint each, but this can vary greatly. Some user breakpoints consume several low-level breakpoints and conversely, several user breakpoints can share one low-level breakpoint. User breakpoints are displayed in the same way both in the Breakpoint Usage dialog box and in the Breakpoints window, for example Data @[R] callCount. C-SPY itself also consumes breakpoints. C-SPY will set a breakpoint if: � the debugger option Run to has been selected, and any step command is used. These are temporary breakpoints which are only set when the debugger system is running. This means that they are not visible in the Breakpoint Usage window. � the Semihosted or the IAR breakpoint option has been selected. These types of breakpoint consumers are displayed in the Breakpoint Usage dialog box, for example, C-SPY Terminal I/O & libsupport module. C-SPY plugin modules, for example modules for real-time operating systems, can consume additional breakpoints. Specifically, by default the Stack window consumes a breakpoint. To disable the breakpoint used by the Stack window: � Choose Tools>Options>Stack. � Deselect the Stack pointer(s) not valid until program reaches: label option.

[sjackson]

Posted on May 17, 2011 at 09:54

I've found that often you can set more breakpoints than just one (though not more than 2 or 3) as long as you do it before you begin debugging.

If you need more breakpoints once you're in the middle of debugging, try disabling a breakpoint at one location and enabling it somewhere else. It's annoying, but it's one way to get around the problem.