Quote:
Originally Posted by ross
command is a bit unstable..
Do not trigger in some situation and vice versa trigger with no reason.
|
Maybe fixed again. (or something else gets broken)
Quote:
2) in debugger (with a machine with 8MB z2 memory) if you type s "something" the response is bad:
|
This goes to category "unsupported". May or may not be fixed someday..
Quote:
3) in machines with cache enabled if you use the 'a' command in debugger the code inserted is unusable if memory location used is in some cache
yes, I know, this is some sort of self modify code, but we need an escape:
a new command in debugger to flush cache (i've tried setting CACR manually but do not works) or simply auto-flush after last 'a' instruction inserted
|
It isn't that simple. 68020+ has long prefetch, it needs reload too if you modify instruction close to current PC and that can't be automatic. (or timing would change each time debugger is exited)
I haven't yet decided how to handle this. Toggleable automatic mode sounds nice but it may be too annoying to implement..
Quote:
4) 'fs' command do not work for me (it may be that I do not use it well..)
from help:
Code:
fs <lines to wait> | <vpos> <hpos> Wait n scanlines/position.
fs n scanline wait works, a defined position don't.
|
Perhaps it works better now but note that it can't be accurate if CPU is blocked, it needs to wait until CPU gets clock cycles.