Emulator

Game Name?

Super Paper Mario, but it doesn't seem to be a game problem

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

R8PE01

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

ba74fb5b6b820b6feb771786180e4c65

What's the problem? Describe what went wrong.

Basically, I did a build of Dolphin with the option to have it in debugfast so i can break memory when they are written or read (it's to check what the game does with them). The feature however rarely works as I try to add known addresses of the game and dolphin can react in many different, but undesirable way. Could be immediate crashes with a segmentation fault error in the terminal (or a breakpoint trap error) or it could just hang and I have to kill it. Sometime, it actually does manages to work, but it's very rare.

What steps will reproduce the problem?

I will pick the X coordinate for this example:

1: start the game.
2: click +MC and put the address 804CD4B4 check read, write and break. (I know it\s the X coordinate address because I could hack it on Cheat engine just fine)
3: this is where it should either crash or hang, if it hangs, you can know this by trying to pause the emulator which should remove any control and force you to kill dolphin.

Which versions of Dolphin did you test on? Does using an older version of Dolphin solve your issue? If yes, which versions of Dolphin used to work?

Dolphin 4.0-8684 (debugfast, built from source). I couldn't test an older version because the latest git source is the only way i found to make a build in debugfast. I do know someone who got it working from an older 4.0 build on Windows 7.

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

I use Linux Mint 17.3 (kernel 4.2-23 generic), mesa 11.2.0 devel.

CPU: intel core i5 4690 3.5 ghtz (quadcore)
GPU: intel hd graphics 4600
8gb of ram.

Is there any other relevant information? (e.g. logs, screenshots,
configuration files)

If the emulator crashes and it was launched from terminal in debug mode, it is possible to see either the error segmentation fault or breakpoint trap. Also, I can edit addresses in the memory editor and it does work so I don;t think it;s because I put an invalid address.