WinUAE debugger trace bug

[b00mer]

While using WinUAE 2.8.1 debugger I have found out that the "z" command doesn't work. It works as if I am using the normal trace command and joyfully steps into the subroutine.

If you can't reproduce it (meaning it's my config issue), I can send more info.

[Toni Wilen]

Works for me. What kind of config?

[b00mer]

Impossible.

I've retried with everything stripped down. I've used either A600 and A1200 quickstart configuration and added PC directory as a HDD. There is no startup-sequence, nothing, just a simple executable with the following code:

clr.w 0
bsr.s a
jsr a
rts
a:
moveq #0,d0
rts

Before I started the executable, I entered the following in the debugger:

w 0 0 2

Starting the executable immediately popups the debugger, and when I enter "z" it jumps to the "a" label.

Is there any other information worth sharing?

[Toni Wilen]

You should try some simpler test first, at least put some extra instruction between each jump instruction.

[b00mer]

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.

[Toni Wilen]

Even when using A500 most compatible quickstart?

[b00mer]

Just tried. The same story.

[Toni Wilen]

Could you attach text copy&paste from debugger console window that shows the problem? (I need to see exactly how to duplicate it)