| |
chatGPZ
Registered: Dec 2001
Posts: 11116 |
VICE debug interface
i want to add some simple mechanisms to VICE that will help with automatic regression testing (there are over 800 test programs now, running them all manually takes several hours) - this stuff might be interesting for coders writing c64 software as well, so before i start i am looking for some more ideas on what might be useful.... the whole thing would be implemented as either a cartridge or some special i/o device, so basically everything should be triggered by writing to certain registers. the minimal functionality i came up with looks like:
- exit vice with exit code (to signal the test suite success or error)
- print a string to console (with some kind of "printf" like functionality, so you can print contents of registers/memory easily)
what else may be useful? |
|
... 32 posts hidden. Click here to view all posts....
|
| |
Endurion
Registered: Mar 2007
Posts: 72 |
Media handling (attach disk/tape)
Warp mode toggling
It might help if you tell what does test programs do |
| |
chatGPZ
Registered: Dec 2001
Posts: 11116 |
what the test programs do doesnt matter at all, as said, what i listed in the first post is sufficient for the testing stuff. all i wanted to know is other things that perhaps could be useful and fit the "everything should be triggered by writing to certain registers" idea. oh well o_O |
| |
Martin Piper
Registered: Nov 2007
Posts: 634 |
Quote: *sigh* i give up. (try -console and -moncommands)
Except on the Windows version the console and monitor commands don't quite offer the combination of functionality that was described.
Last version I tried it with VICE 2.4:
x64.exe -console
Result: VICE Error! Cannot set cooperative level: Parameter not valid
If I use: x64.exe -moncommands monitorExec.txt
Where monitorExec.txt contains:
l "C:\work\C64\BlankProjectComp\BlankProjectComp.prg" 0
w c000
g 80d
Then VICE (the whole Windows process, not the C64) crashes. :) |
| |
Testicle
Account closed
Registered: Sep 2002
Posts: 131 |
Quote: *sigh* i give up. (try -console and -moncommands)
You seem to have a very low frustration tolerance limit. ;-) |
| |
chatGPZ
Registered: Dec 2001
Posts: 11116 |
not at all, i just dont plan to continue this discussion when noone bothers to even read the question.
and i dont care about people not being able to use a proper shell (nor filing a proper bug report) either :) |
| |
Stone
Registered: Oct 2006
Posts: 168 |
@Martin: I have used VICE scripting to automate song compiling with my native tracker. I modified the compiler to jump to a certain address ($cfff) after completion. This works even with VICE 2.4 on windows.
The command line I use is something like this:
x64.exe -drive8type 1541 -drive9type 1541 -autostart autocomp.d64 -9 temp.d64 -moncommand commands.txt -warp -logfile vice.log +sound -console
commands.txt is
break cfff
command 1 "quit"
(Sorry for staying off topic..) |
| |
chatGPZ
Registered: Dec 2001
Posts: 11116 |
btw, that stuff isnt suited for the testsuite, because having a very simple "test cartridge" as described in the first post makes it possible to use the testsuite with another emulator with very little effort for the emulator author (i expect at least bero to jump on it as well once implemented) |
| |
Martin Piper
Registered: Nov 2007
Posts: 634 |
Quote: @Martin: I have used VICE scripting to automate song compiling with my native tracker. I modified the compiler to jump to a certain address ($cfff) after completion. This works even with VICE 2.4 on windows.
The command line I use is something like this:
x64.exe -drive8type 1541 -drive9type 1541 -autostart autocomp.d64 -9 temp.d64 -moncommand commands.txt -warp -logfile vice.log +sound -console
commands.txt is
break cfff
command 1 "quit"
(Sorry for staying off topic..)
Interesting. The +sound parameter allows -console to work without an error.
However there still doesn't seem to be a way to automatically save a BMP screenshot from the emulator and then quit once the breakpoint is hit.
The monitor "command" wants to use quotes and the scrsh command expects quotes so they're not compatible with each other. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11116 |
what about the "screenshot" command? *sigh* |
| |
Martin Piper
Registered: Nov 2007
Posts: 634 |
Quote: what about the "screenshot" command? *sigh*
As I said above:
The monitor "command" wants to use quotes and the scrsh (screenshot) command expects quotes *so they're not compatible with each other.*
Unless you escape the command's quotes. Which isn't documented. |
| Previous - 1 | 2 | 3 | 4 | 5 - Next |
