Project

General

Profile

Emulator Issues #11874

Debugger: Memory value input ignores leading zeros

Added by Rena about 1 month ago. Updated 4 days ago.

Status:
New
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?

N/A

Game ID? (right click the game in the game list, Properties, Info tab)

N/A

MD5 Hash? (right click the game in the game list, Properties, Verify tab, Verify Integrity button)

N/A

What's the problem? Describe what went wrong.

The Memory view of the debugger UI ignores leading zeros in the Value field, making it difficult to write a multi-byte value that begins with zero.

What steps will reproduce the problem?

  1. Navigate to any address in the memory view
  2. Enter eg "00000042" in the Value field
  3. Click "Set Value"
  4. Observe that only one byte was changed (to 0x42) rather than four (to 0x00, 0x00, 0x00, 0x42) as expected

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

5.0-10916 (at least this is the latest version in AUR)

Is the issue present in the latest stable version?

No (5.0-7309, latest version in Pacman)

If the issue isn't present in the latest stable version, which is the first broken version? (You can find the first broken version by bisecting. Windows users can use the tool https://forums.dolphin-emu.org/Thread-green-notice-development-thread-unofficial-dolphin-bisection-tool-for-finding-broken-builds and anyone who is building Dolphin on their own can use git bisect.)

beats me

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

  • CPU: AMD FX-8320E Eight-Core Processor
  • GPU: Radeon RX980
  • RAM: 32GB
  • OS: Arch Linux

Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)

History

#1 Updated by Rena 4 days ago

In at least version 5.0-11197, this bug seems to affect the Copy Hex function in the memory view. It will copy 8 digits starting from the first nonzero, which may even be in the middle of a byte.

Also available in: Atom PDF