??? 09/04/07 12:10 Read: times |
#143984 - trace, limited resources Responding to: ???'s previous message |
Richard Erlacher said:
Keep in mind that I prefer not to use a PC and software running on it to perform a debug session. Assume I'm using a terminal. Do you mean a real VT52 or alike? That's no better to carry around than a PC... :-) OK I was joking. I see the merit of being independent of OS and similar stuff - have you ever heard me praising BASIC52? :-) Richard Erlacher said:
Isn't a trace just a series of repeated and moved breakpoints? No. I've repeated it already, please reread carefully. For single-step and tracing, you DON'T need to place a breakpoint-jump into the code. Richard Erlacher said:
The monitor I prefer is 8KB in size[...] That's quite prohibitive for the OP's applications, where both mentioned derivatives have... guess... 8kB of code FLASH... :-) 1kB is a maximum target. In this case, even the ascii output of numbers sounds like an unaffordable luxury... Richard Erlacher said:
Are you suggesting one should ship such a monitor as part of the deliverable code? No, contrary. As I said, I did not understand your remark. You were stating that I should deliver the same thing I was debugging - I deduced from this, that you suggest to include the monitor. JW |