[hatari-devel] Getting OS call opcode from stack?
Eero Tamminen
eerot at users.berlios.de
Fri Jun 25 17:12:33 CEST 2010
Hi,
On Friday 25 June 2010, Vincent Rivière wrote:
> > Does the 201 version have also a Control array like the rest of the AES
> > calls, with some opcode in it?
>
> No.
>
> > Or should I just map anything having 201
> > in D0 (when trap(2) is called) to appl_yield() opcode (17)?
>
> Yes.
Thanks, I fixed the VDI & AES handling accordingly:
http://hg.berlios.de/repos/hatari/rev/4174ef707bf2
Btw. If there's anything else that could be interesting to track in general
(like currently these opcodes and earlier HBL & VBL variables are), I could
add them also as variable, just ask! It's easy to do as internally they're
just small functions in the debugger breakpoint code. :-)
- Eero
PS. In the EmuTOS case, I think it's most convenient to have these
breakpoints specified in a file and given to Hatari when in starts, like
this:
-------- debug.ini ---------
b LineAOpcode ! LineAOpcode && LineAOpcode < 0xffff :trace
----------------------------------
$ hatari --parse debug.ini ...
More information about the hatari-devel
mailing list