I'll get on that soon (I hope; if not, I may just host the code through different means temporarily).
Anyway, it seems what I mentioned about a timer is different than what you've discussed. For one, the timer I was talking about was stored in WRAM and manually operated by user (my) code.
It was just a lame hack to make sure that an amount of time that was "long" relative to the speed of the processor but "short" relative to the debugger (here referring to the person doing the debugging, not the debugging tool) would elapse before any attempt to locate another instruction to trap was made.
And as I've mentioned, the code I had running (and tested with small success in one case) advanced through memory, not execution, therefore being prone to difficulties with dynamic code. Because the instructions it was trapping as such were not always being executed, there was less slow down, but also the possibility for missing hits.
If you'll pardon the oxymoron.
Post whatever you like from the conversation, though hopefully the code will speak for itself. I want to warn you (again?) that it's not my best work, and that if it had been, it still would be sub par. Or rather, I imagine its reception would suggest so.Edit:
The code is from 2 Christmases ago (yet another Christmas I spent coding in assembly instead of spending time with friends and/or family - at least this time I wasn't hand assembling my code!).
So, yeah, that's my excuse, if you don't like it. Edit, again:
Actually, Para, can you go ahead and set up and/or explain how to use a repository at the hg.kodewerx domain for this particular component of the SRDP's reach?