Project

General

Profile

Actions

Emulator Issues #10590

closed

Wrong PC addresses in memory breakpoint log

Added by aldelaro5 about 6 years ago. Updated almost 6 years ago.

Status:
Fixed
Priority:
Normal
Assignee:
-
% Done:

0%

Operating system:
N/A
Issue type:
Bug
Milestone:
Regression:
No
Relates to usability:
No
Relates to performance:
No
Easy:
No
Relates to maintainability:
No
Regression start:
Fixed in:

Description

Game Name?

Eternal Darkness Sanity's Requiem

Game ID? (right click the game in the game list, properties, info tab)

GEDP01

MD5 Hash? (right click the game in the game list, properties, info tab, MD5 Hash: Compute)

c784fa979dec9f2c38259b878138fda5

What's the problem? Describe what went wrong.

When adding a memory breakpoint set to write with break and log, the game will pause properly at the right addresses, however, the logs reports a wrong PC addresses. I only know it affects Windows 10 and not my Arch Linux for the same revision.

What steps will reproduce the problem?

1: start Dolphin in debug mode (-d argument) on Windows
2: go to log configuration, put the logs to notice level and make sure MI & Memmap is checked
3: Start the game, pass the intro cutscene until you get character controls
4: Add a memory breakpoint at address 8122A9A0 on write with break and log (it coresponds to your character's position in the X axis)
5: check the code view, a psp_st instruction should be the current isntruction at address 80205fb0
6: check the logs, something like this should appear:

22:03:010 PowerPC\BreakPoints.cpp:248 N[MI]: MBP 801241e4 ( --- ) Write64 00000000f379cfc2 at 8122a9a0 ( --- )

This PC address is wrong, it did not wrote from the instruction at 801241e4, but at 80205fb0

Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.

I tested on 5.0-5053 and 5.0-5636 in Windows 10, they both gave the same issue.

Is the issue present in the latest stable version?

I do not know

What are your PC specifications? (CPU, GPU, Operating System, more)

CPU: intel core i5 4690
GPU: NVIDIA GeForce GTX 950
OS: Arch Linux
RAM: 8Gb

Though, I used a virtual machine to test on Windows 10, I had someone had this issue on a real machine and I got the same problem on this VM.

**Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,

It may happen on all games, I don't know, but this method is very consistent to reproduce it.

Actions #1

Updated by ryanebola16 about 6 years ago

Sounds related to #10589

Actions #3

Updated by PPLToast almost 6 years ago

Yeah it's fixed now.

Actions #4

Updated by JosJuice almost 6 years ago

  • Status changed from New to Fixed
Actions

Also available in: Atom PDF