English Amiga Board - View Single Post

b00mer · 19 August 2014, 16:29

I did this already, no change. Initially I was tracing much more complex program than this.

However, I've just tested the "z" command without starting my executable on A600 config and thus not using "w" command. It worked ok when I was tracing the ROM code (jsr at $f8175a).

Could "w" command somehow influence the outcome of the "z" command?

On a side note, how come if I use "z" command on branch, jump or return usually (not always) make further debugging impossible (infinitely scrolling exception message)? I remember the equivalent "e" command having the same problem in Timo's Amiga Monitor.

By continuously switching between "t" and "z" you can quickly make a mistake and render further debugging impossible.

19 August 2014, 16:29	#5
b00mer Registered User Join Date: Jul 2014 Location: MB / Slovenia Posts: 15	I did this already, no change. Initially I was tracing much more complex program than this. However, I've just tested the "z" command without starting my executable on A600 config and thus not using "w" command. It worked ok when I was tracing the ROM code (jsr at $f8175a). Could "w" command somehow influence the outcome of the "z" command? On a side note, how come if I use "z" command on branch, jump or return usually (not always) make further debugging impossible (infinitely scrolling exception message)? I remember the equivalent "e" command having the same problem in Timo's Amiga Monitor. By continuously switching between "t" and "z" you can quickly make a mistake and render further debugging impossible. Last edited by TCD; 20 August 2014 at 20:28. Reason: Back-to-back posts merged.