breakpoints showing different module when stopped

[martinlockner]

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.

[BlackNight · Accepted solution]

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

[martinlockner]

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