Re: [cc65] Debugging stack overwrite problem

Hi!

On Thu, Nov 22, 2012 at 10:55:23PM +0200, Karri Kaksonen wrote:
> Obviously I have some routine that is overwriting the stack. Are
> there any tools to find what it could be?

I've successfully debugged similar problems using memory write breakpoints in
VICE. Any emulator will do that is able to set a breakpoint on write to a
memory area. So load the code into the emulator, run until after the first
write to the variable, the check the stackpointer and set a breakpoint on the
first 10 or 20 bytes on top of the stack.

Another possibility to at least narrow the problem down is to check the
relevant memory cells in an interrupt handler, but this needs extra code
within the executed program.

Regards


        Uz


-- 
Ullrich von Bassewitz                                  uz@musoftware.de
----------------------------------------------------------------------
To unsubscribe from the list send mail to majordomo@musoftware.de with
the string "unsubscribe cc65" in the body(!) of the mail.