topic breakpoints showing different module when stopped in CodeWarrior for MCU

breakpoints showing different module when stopped

martinlockner — Fri, 31 Jan 2014 14:18:14 GMT

I am using Codeworrior 10.4 with a mc9s08dz128 and I have noticed that when a breakpoint occurs (using debug) that sometimes the displayed code is in a different "C" module than where the breakpoint is set. This makes it difficult to single step to try and troubleshoot a section of code. Is this a common problem? Is something out of sync?

Thanks,

Marty L.

Re: breakpoints showing different module when stopped

BlackNight — Fri, 31 Jan 2014 14:21:21 GMT

Hello Marty,

are you using the banked memory model? Could it be that the breakpoint is set for the code in another code bank?

Check as well the 'breakpoint view': you can check to which source file the breakpoint belongs.

Erich

Re: breakpoints showing different module when stopped

martinlockner — Fri, 31 Jan 2014 14:28:42 GMT

Erich,

I am using the banked memory model. I am setting the breakpoints in my ‘C’ source code and when I look at the breakpoints under the ‘Breakpoints’ tab that show the correct module name and line number.

Thanks,

Marty