Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

memory.read crash when debugging with Ghidra #17851

Closed
4 of 5 tasks
Nemoumbra opened this issue Aug 5, 2023 · 1 comment · Fixed by #18104
Closed
4 of 5 tasks

memory.read crash when debugging with Ghidra #17851

Nemoumbra opened this issue Aug 5, 2023 · 1 comment · Fixed by #18104
Labels
Milestone

Comments

@Nemoumbra
Copy link
Contributor

Game or games this happens in

Not game-specific

What area of the game / PPSSPP

Process > Memory > Uncached Kernel Memory in the Ghidra Debugger causes it to make a remote API request "memory.read".
This results in the function Base64Encode accessing something that it can't access (line 16 in Base64.cpp). The uncaught exceptions are scary.
Now then, the image.
image

What should happen

Either reject the memory access or not crash.

Logs

This is the command that Ghidra issued: {"address":3355443200,"size":4096,"replacements":false,"ticket":"705f3106-40e8-4a97-ae12-9af9084dbe13","event":"memory.read"}
3355443200 == 0xC8000000

Platform

Windows

Mobile phone model or graphics card

AMD Radeon(TM) Graphics

PPSSPP version affected

Self-built version (one of the lastest)

Last working version

No response

Graphics backend (3D API)

Direct3D 11

Checklist

  • Test in the latest git build in case it's already fixed.
  • Search for other reports of the same issue.
  • Try resetting settings or older versions and include if the issue is related.
  • Try without any cheats and without loading any save states.
  • Include logs or screenshots of issue.
@Nemoumbra
Copy link
Contributor Author

I've got some more info. You don't have to use the Remote API to debug this issue. Just enter 0xC8000000 in the Memory Viewer's "goto" field.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants