> > So are you trying to say that all BSR and JSR calls can't be intercepted by the
> MAME
> > 6809 emulator and their text equivalent pushed onto a list control? e.g.
>
> Sure you can, but that isn't anything like what a call stack is.
>
> You'd need to prune the list when you rts, taking into account that your rts might be
> on a different stack than the last JSR or the address might have been pushed onto the
> cpu stack as an indirect jump.
>
> (forgive me it's 6502 as it's the assembly I wrote the most)
>
> JSR myroutine
> RTS
>
> :myroutine
> LDA #$d0
> PHA
> LDA #$c0
> PHA
> RTS
>
> Some cpu's can move the stack pointer for multitasking, others can just copy the
> whole stack somewhere and restore it. When you do that the call stack is going to be
> even more messed up.
No, it's not a true call stack but it's a list of calls in a LIFO order, is that better 
I would like the last 10 or so JSR and BSR to be logged somewhere. I would like to click on an entry on the log and go back to the relevant line of assembly .
I don't care about when RTS is hit, I just want to have a quick look of the subroutine being called, see if I recognise what it does, and if not quickly go back to the JSR and step over it.
Right now, I have to put a breakpoint on the RTS, run to that, but sometimes that's not really what I'm after, especially if PC is changed by something unexpected.
Right now I'm reverse engineering Robotron 2084, there are a lot of indirections, many JSRs that call JMP instructions, and these are quite hard to keep track of UNLESS I step through the function in its entirety and return to the caller that way.
|
Index 
Flat 
Re: Debugging 6809 RAM writes with MAME debugger (Robotron 2084)
Reply
