Re: 65C02 assembler / trace

From: smf <smf_at_null.net>
Date: Sun, 30 Sep 2018 12:24:52 +0100
Message-ID: <0873ec56-d726-5a6b-8746-e7a22c66a32d@null.net>
On 30/09/2018 07:17, David Holz wrote:
>
> 2) Temporarily place a BRK where the PC is going to be after the next
> instruction runs.  You'd have to anticipate the destination of branches
> and jmp/jmp()/jsr/rts/rti.  For all other cases, just the length of the
> upcoming instruction is needed.  This can fail if an instruction is
> selfmodding the next opcode, dealing with ROM, or doing memory bank
> stuff, but can be friendly to interrupts running in the background.

3) emulate instructions which can change the program counter & copy code 
into a buffer and put a jmp instruction after it. So you can trace rom.

https://github.com/jefftranter/6502/tree/master/asm/jmon
Received on 2018-09-30 14:02:50

Archive generated by hypermail 2.2.0.