Erik, as you probably already have noticed, the "C-hatred" is mostly showoff.

However, the ICE does not debug in C - it "debugs in C" rather. As the advertisement goes - "C-source debugging" - well, that's simply not true, as it is with most of the advertisements. What we see, is debugging in asm, plus a tool mapping the breakpoints, statements, etc., in a very primitive and straighforward way into the C source (or .lst or whatever).

So, shortly put, the path from C-source to asm (hex) is rather complex, the debugging it performed on asm level, but there is only a simplistic, rudimentary way back to reflect the status of debugger in C.

That's exactly what you are complaining at - the single breakpoint for two functions. The same happens with the various weirdly register-mapped, or completely optimized out, variables.





I said, ideally. In the ideal world, the cost is not an issue :-) . I know you are man of the present and reality - but the toolmaker (Ryan) here asked for vision, didn't he... He knows the reality already too well so we don't need to repeat that for him.

In this philosophic line, there are too many things around, which came out from the "this can be done" philosophy. I would like to have more things around arising from the "this would be nice to have" way of thinking...

JW