No way to know when VICE stops because of AdvanceInstruction
Autostart binary monitor should pause after set
Perhaps one more question. I'm trying to figure out how to best start profiling right before my app starts. Here is one plan: put VICE in paused mode Autoload (with run after load = true) the app Issue AdvancedInstructions command Now, this does not work because autoload with run after load doesn't honor paused state and restarts the emulator. What would be the proper way to start an autoloaded app (run after load=false)? By setting a PC register to its start location? TIA
OTOH OTOH recording 8192 instructions takes roughly half a second (including communication through binary monitor) so stopping only when buffer is full shouldn't mater.
Hm, OTOH there is one more issue - the last fetch. When app stops collecting, how does it know how many items to retrieve? It's certainly N<BufferSize, but how would it know?
Setting buffer size will only slightly help, will allocate everything upfront (it might be huge) and it's still a fixed buffer size. Advance instructions might actually do the trick, good idea. I assume (the docs for IC) mean "How many instructions to execute or to step over based on SO"? IOW if I set SO to false, it will just execute N instructions whatever they are. From docs: SO: 1 byte: Step over subroutines? Should subroutines count as a single instruction? IC: 2 bytes: How many instructions...
Enhance CPU History binary command
For the time being I've solved it like this - I read the SYS address from .prg, set a temporary checkpoint to that address for EXEC, AutoStart the app (not just AutoLoad) and wait for checkpoint being set. Once checkpoint is hit I know app is hot and ready.