??? 06/02/07 08:33 Read: times |
#140188 - That's exactly the problem! Responding to: ???'s previous message |
Erik Malund said:
... a good ICE will "debug in C" Jan Waclawek said:
... the ICE does not debug in C ... 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). Yes, that is exactly the problem: the ICE (and any other debugger I've seen) actually works at the machine instruction level, and then tries to map that back to 'C' source statements. The trouble is that this mapping is very crude, and breaks with even the simplest optimisations. This is what the toolmakers really need to work on: a mapping that can relate highly-optimised machine code back to its original source. As I suggested earlier, this will (probably) need a high degree of cooperation between the code-generation toolmakers and the debug toolmakers; eg, the code-generation tools are going to have to provide significantly enhaced debug information to enable the debug tools to make sense of their optimised output! |