English Amiga Board


Go Back   English Amiga Board > Support > support.WinUAE

 
 
Thread Tools
Old 04 February 2023, 15:45   #1
kamelito
Zone Friend
 
kamelito's Avatar
 
Join Date: May 2006
Location: France
Posts: 1,801
Bug in WinUAE debugger or in me?

Version 64bit 4.10.0

WinUAE debugger 4.10.0 2022 12 18 64bit?

I was expecting the code to go to $c65e and not $c666

it is a bug right?

>m 1a16
00001A16 7F00 0700 42B9 0000 6B24 4239 0000 1E72 ....B...k$B9...r

>d c650
0000c650 c482 and.l d2,d2
0000c652 4e75 rts == $000015c2
0000c654 0c39 007f 0000 1a16 cmp.b #$7f,$00001a16 [7f]
0000c65c 6608 bne.b #$08 == $0000c666 (F)
0000c65e 08f9 0005 0000 c482 bset.b #$0005,$0000c482 [00]
0000c666 0c39 0077 0000 1a16 cmp.b #$77,$00001a16 [7f]
kamelito is offline  
Old 04 February 2023, 16:36   #2
a/b
Registered User
 
Join Date: Jun 2016
Location: europe
Posts: 1,039
Use HH <number_of_instructions> to get full info on cpu''s what&why.
a/b is offline  
Old 04 February 2023, 17:02   #3
ross
Defendit numerus
 
ross's Avatar
 
Join Date: Mar 2017
Location: Crossing the Rubicon
Age: 53
Posts: 4,474
WinUAE (when disassemble) uses the instantaneous value of the flags (check the SR value and you will see that you have the 'right' Z).
It can't know that in advance except by emulating the instruction stream!

Sure, it's easy for you to see 'by eye', but it can't know if any code modifies the contents of the cell before it gets to that point in the code.
ross is offline  
Old 06 February 2023, 07:46   #4
kamelito
Zone Friend
 
kamelito's Avatar
 
Join Date: May 2006
Location: France
Posts: 1,801
The executed code is c566
kamelito is offline  
Old 06 February 2023, 09:45   #5
ross
Defendit numerus
 
ross's Avatar
 
Join Date: Mar 2017
Location: Crossing the Rubicon
Age: 53
Posts: 4,474
Quote:
Originally Posted by kamelito View Post
The executed code is c566
I assume you mean C666.

This simply means that somewhere else in the code (an IRQ?) that cell (1A16) has been modified.
It wouldn't be so strange, it's basically the function of that piece of code since it looks like a switch construct.

But if you want to remove any doubts put a breakpoint at C65E or C666, then check the offending cell.
If instead the cell contains 7F then it's a bug
ross is offline  
 


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools

Similar Threads
Thread Thread Starter Forum Replies Last Post
WinUae 4.4.0 - Action replay bug/ Load Config bug Dan support.WinUAE 2 20 July 2020 07:59
WinUAE fa debugger command bug jotd support.WinUAE 2 15 September 2018 18:19
Debugger updates (was: WinUAE Debugger HH PC history) selco support.WinUAE 8 14 March 2018 22:27
wishlist: Creating states from debugger and other bits, and one bug ref support.WinUAE 7 17 February 2015 05:11
WinUAE debugger trace bug b00mer support.WinUAE 7 23 August 2014 15:37

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +2. The time now is 08:58.

Top

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.
Page generated in 0.06646 seconds with 15 queries