CodeWarrior for MCUのトピックPlacing breakpoint

Placing breakpoint

etolocka — Sat, 17 Nov 2007 04:35:07 GMT

Hi

I´m using CW 5.1 to program a GT60 micro using C. Sometimes, I can´t place a breakpoint where I want in the code, and CW moves it to a near instruction. Why?

Thankfully,
Ernesto.

Re: Placing breakpoint

Witztronics — Sat, 17 Nov 2007 10:41:20 GMT

Many times this happens when you try to place a breakpoint at a label, comment or on code that has been stripped out by the compiler as dead (not used) code.

Re: Placing breakpoint

BlackNight — Sat, 17 Nov 2007 16:56:39 GMT

Hello,
a good tip is to enable Marks in the debugger (source window context menu, or menu Source > Marks): then the debugger shows with marks in the source window where line debug information is available (where you can set a breakpoint). I have this enabled by default.

BK

Re: Placing breakpoint

etolocka — Fri, 23 Nov 2007 20:28:17 GMT

Hi!

I´m trying to place the breakpoint at a executable instruction, not a label or dead code.

Regards,
Ernesto.

Re: Placing breakpoint

etolocka — Fri, 23 Nov 2007 20:31:02 GMT

Enabling "marks" I can see that there is no debugging info where I want to place the breakpoint. Why? Can I force the compiler to do this?

Regards,
Ernesto.

Re: Placing breakpoint

BlackNight — Sat, 24 Nov 2007 01:10:44 GMT

Hello,
well, that really depends a little bit of that source code. Maybe you just did a mistake like
if (ui == -1) ....
and if the variable is unsigned, the compiler may have optimized the whole block away? In such a case, the compiler would have you warned about that (with a message). I suggest that you check the compiler messages around the code in question (maybe you simply did an error in the source code?).

If this is not the reason, you may switch off optimizations, and here are some options you could try:
-Onu
-Onf
-O0
-Ona
-Onb
-Ont

If the code is around a variable, you can enforce disabling optimizations making the variable volatile (but this is really only something as a last resort: typically the compiler is right optimizing code).

BK