|
|
Post by oziphantom on May 3, 2019 11:31:18 GMT
actually the killer feature would be break 9bits having the monitor understand the difference between the two banks and not fire break points on 8bits would be gold dust
|
|
|
|
Post by bjonte on May 3, 2019 18:27:42 GMT
actually the killer feature would be break 9bits having the monitor understand the difference between the two banks and not fire break points on 8bits would be gold dust Oh yes. I want that very badly. I hacked my version of Vice to do that since I’m going crazy otherwise. |
|
|
|
Post by bjonte on May 3, 2019 19:11:39 GMT
Actually the optimal solution is to be able to set breakpoints in different types of RAM and ROM as well. It is a big difference between a write breakpoint in color RAM and one in the general purpose RAM at the same address.
|
|
|
|
Post by willymanilly on May 4, 2019 3:07:16 GMT
I've done some updates to the Machine Monitor and uploaded to the website. I haven't implemented full 17 bit address debugging but using a combination of io d500 and switching to either bank using rb0 and rb1, it should be reasonably clear which bank is active and/or being disassemble/dumped. If you notice any bugs or annoyances let me know. The summary of changes as stated on the website are:- - Updated C128 Machine monitor commands rb0 and rb1 to no longer mess with MMU.
rb0 - debug using memory in RAM bank 0
rb1 - debug using memory in RAM bank 1
system - debug using system view of memory (defaults back to this when exiting monitor)
- breakpoints for c128 now have 17 bit range:-
bk e000 will set a breakpoint at bank 0 location e000
bk 1e000 will set a breakpoint at bank 1 location e000.
Actually the optimal solution is to be able to set breakpoints in different types of RAM and ROM as well. It is a big difference between a write breakpoint in color RAM and one in the general purpose RAM at the same address. Yes, version 2 of Z64K will have this and more! It will still be awhile before it's ready to be released though so I will be still doing updates to the existing Monitor.  |
|
|
|
Post by oziphantom on May 4, 2019 5:55:38 GMT
I made an extra debugger for x128 that shows me where things are actually referencing pic here postimg.cc/dkFKshwx for those "why does this jsr fail.. oh wait why is there ROM there.." moments I need to get it into VICE PDB Debugger. I also added the can read a value in a breakpoint condition, so you can do things like break $4056 if @io:D500 > 63 |
|
|
|
Post by bjonte on May 4, 2019 7:23:02 GMT
I made an extra debugger for x128 that shows me where things are actually referencing pic here postimg.cc/dkFKshwx for those "why does this jsr fail.. oh wait why is there ROM there.." moments Nice one! |
|
