English Amiga Board - View Single Post - UAE debugger updates (executable debugging, segment tracking, symbols and more)

Toni Wilen · 13 May 2018, 08:38

Only difference is extra long word in stack, it shouldn't have any effect unless you previously used every byte of the stack which is very unlikely

After initial break, add dummy breakpoint (f 0 for example), then g. When first invalid access comes, use H command to see history of executed commands. (up to last 500 instructions). It should help to find out what happened.

EDIT: stack frame commands may also help.

13 May 2018, 08:38	#69
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,539	Only difference is extra long word in stack, it shouldn't have any effect unless you previously used every byte of the stack which is very unlikely After initial break, add dummy breakpoint (f 0 for example), then g. When first invalid access comes, use H command to see history of executed commands. (up to last 500 instructions). It should help to find out what happened. EDIT: stack frame commands may also help. Last edited by Toni Wilen; 13 May 2018 at 08:44.