| ??? 06/01/07 06:16 Read: times |
#140135 - Yes, that's the challenge Responding to: ???'s previous message |
Neil Kurzman said:
The Optimizer can combine lines of code so there is no place to break. How could the debugger know how to break it back down? Sure, it can't bring them back - but it could do a far better job of showing you what has been optimised-out, etc. It is also for example switch statment with common tail ends are combined. True; and not just switches - Keil can also combine common entry & exit code for functions. The debugger would have to look at the preceding steps to figure out how you there. If the debugger could at least show you how the actual machine code relates to source lines, that'd be a big help. Currently, you're on your own, and have to do it all manually The same with variables. The compiler may choose to eliminate imtermediate variables. The debugger can not bring them back. Again, if the debugger would at least show you what's happened, that would be a big help! |



