??? 02/27/07 13:16 Read: times |
#133796 - a common issue Responding to: ???'s previous message |
Very convenient, and it works for me. However, it does give me a problem when I come to use my Metalink ICE as for some reason the trace doesn't "follow" the code into the included files (hope that makes sense), which can be a real pain in the proverbials.
Has anyone come across a fix for this? An include in metalink evidently run the same way as most emulators treat macros. For some reason the structure of the debug info in the generated files comes out as "a macro is an instruction". My 'common' example is Keil compile and Ceibo emulator where the emulator will stop at the macro, but not step through it unless I switch to assembler stepping where it will step through it but with no source display. Again, since this must be related to the debug info in the .abs (Keil) or whatever file metalink produces for this and thus I doubt "anyone come across a fix for this". The Metalink assembler, of course, do (did?) suffer from the absence of a linker and thus the include method is the 'tried and true' method of 'linking' What I did, in those days, was to utilize my Brief (r.i.p) editor to include the include (i.e. include the code, not an include statement) while debugging and then changing it to an include statement for the final version. Erik |