topic Re: Codewarrior steps through assembly code, not C code. in Classic/Legacy CodeWarrior

Codewarrior steps through assembly code, not C code.

triplell — Thu, 07 Oct 2010 04:21:06 GMT

I have been looking all day and can't find anywhere so that when I'm stepping through code using codewarrior and the BDI2000 debugger that it will step line at a time as opposed to stepping through the assembly.

I changed the view to view source code, however I have to step multiple times to execture every command.

Does anyone know a quick fix?

Re: Codewarrior steps through assembly code, not C code.

CompilerGuru — Thu, 07 Oct 2010 09:42:42 GMT

Without knowing which CW you are using to debug which architecture I don't think we can help. Please provide all the info as requested by the "[IMPORTANT] When Asking about CODEWARRIOR !!!" sticky post in the head of this forum.

Wild guess: Are you building with debug information?

Daniel

Re: Codewarrior steps through assembly code, not C code.

triplell — Fri, 08 Oct 2010 02:10:42 GMT

- Which CPU are you targeting: MPC860
- Which version of CodeWarrior are you using? 5.7.0

Using ABATRON BDI2000 hardware debugger.

Re: Codewarrior steps through assembly code, not C code.

CrasyCat — Fri, 08 Oct 2010 17:01:14 GMT

Hello In order to be able to step at assembly language level: - On the bottom of the thread window (The window where you are performing the debugging) change the View mode from "Source" to "Mixed" or "Assembly" (Depending if you want to see assembly language only or mixed C and assembly in the Source pane). All stepping feature (Step into, Step Over, ...) will now apply to assembly instructions. CrasyCat

Re: Codewarrior steps through assembly code, not C code.

dyoung — Thu, 17 Jan 2013 16:32:16 GMT

Hi, has there been a solution reached for this problem? I am encountering similar problems while trying to debug a MPC855T using the BDI2000 with Codewarrior Classic for PA v8.8.5.

After hitting a breakpoint, I can step through assembly code and "mixed" view assembly just fine. When I try to step through the C in "source" view, the protocol log shows bunches of stuff happening, but the program counter never advances. Furthermore, when instructing it to go (F5), it immediately breaks and never advances past the current line, even after removing the breakpoint.

Re: Codewarrior steps through assembly code, not C code.

dyoung — Mon, 21 Jan 2013 16:04:58 GMT

After further testing, I've found that something about setting or reaching a breakpoint causes the instruction cache line corresponding to the breakpoint location to become corrupted. That is, it is no longer a reflection of the actual instruction memory. When I disable cache, either in my program, or in the debugger, I am able to step past the breakpoint. This problem occurs for me when using either the USBTAP or the BDI2000. I do not wish to disable the cache - anybody have any experience with this issue?