Skip to content

Fix Memory Breakpoints (MBP) Debugging#184

Open
rapito wants to merge 6 commits intoproject-slippi:slippifrom
rapito:fix-memory-debug
Open

Fix Memory Breakpoints (MBP) Debugging#184
rapito wants to merge 6 commits intoproject-slippi:slippifrom
rapito:fix-memory-debug

Conversation

@rapito
Copy link
Copy Markdown
Contributor

@rapito rapito commented Aug 20, 2020

This fixes the following:

  • Adding/Removing a memory breakpoint will now properly pause when on.
  • Adding/Removing a memory breakpoint while the game is running no longer crashes dolphin.
  • Adding/Removing a memory breakpoint now properly updates the table entries on the breakpoints tab.
  • DebugFast and Debug configurations can now be built using Visual Studio.

Things to know:

  • Use DebugFast run configuration instead of Debug since it will run the game a lot faster than Debug (which is very slow).
  • If you build any Release Configuration then you must rebuild the whole solution (I think) on DebugFast to be able to hit breakpoints again. (I got too tired to figure this out)
    i.e:
    • Build DebugFast: breakpoints are working properly
    • Build Release
    • Build DebugFast again: breakpoints no longer work.
    • Rebuild Solution in DebugFast: breakpoints are working again.

rapito added 5 commits August 20, 2020 02:08
Use proper range depending on the data type when adding a breakpoint.
+ Always Break when a memcheck is hit
+

Mergeback from mainline
-  Add Breakpoints on a CPU thread
+ Use mainline memchecks instead of commented out code (actually hit a breakpoint)
+ Use 142 buildtools as all other projects
+ pass in -d argument to dolphin on run
Don't Memcheck if disabled
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants