Menu

#2213 CPU history shows incorrect values

v3.x
closed-fixed
gpz
None
Monitor
2026-03-20
2026-03-12
rice123
No

Activate monitor, then execute:

dev 8:
a 700
.0700  jsr $ff4b
.0703  jmp $0700
.0706
r pc = 700
step
step
step
step
chis

Result:

.8:0700  20 4B 00    JSR $004B      A:ff X:0a Y:ff SP:45 ..-....C      3192095
.8:ff4b  45 9A       EOR $9A        A:ff X:0a Y:ff SP:43 ..-....C      3192101
.8:ff4d  4C 25 EB    JMP $EB25      A:fc X:0a Y:ff SP:43 N.-....C      3192104

JSR $004B is not what happened.

Discussion

  • gpz

    gpz - 2026-03-12

    For the records: this happens ONLY on the drive, neither x64 (old CPU core, same as drive) nor x64sc show this

     
  • gpz

    gpz - 2026-03-12

    try r46026 :)

     
  • rice123

    rice123 - 2026-03-12
    .8:0700  20 4B FF    JSR $FF4B      A:00 X:00 Y:02 SP:45 ..-...ZC      5130723
    .8:ff4b  45 9A       EOR $9A        A:00 X:00 Y:02 SP:43 ..-...ZC      5130729
    .8:ff4d  4C 25 EB    JMP $EB25      A:03 X:00 Y:02 SP:43 ..-....C      5130732
    

    Thanks for the fix.

    Btw, I spotted another chis bug earlier where the whole JSR instruction was replaced with a JAM (0x02) in the C64 CPU history:

    .C:ed23  78          SEI            A:28 X:01 Y:00 SP:f9 .V-..I..    140626587
    .C:ed24  02          JAM            A:28 X:01 Y:00 SP:f9 .V-..I..    140626589
    .C:ee97  AD 00 DD    LDA $DD00      A:28 X:01 Y:00 SP:f7 .V-..I..    140626595
    

    but I couldn't reproduce it on a fresh VICE instance so the required steps remain unknown.

     
  • gpz

    gpz - 2026-03-20

    closing this - please make a new ticket if you figure out how to trigger that JSR/JAM problem

     
  • gpz

    gpz - 2026-03-20
    • status: open --> closed-fixed
    • assigned_to: gpz
     

Log in to post a comment.

MongoDB Logo MongoDB