Dolphin Debug find out feature

[Brandondorf9999]

The codes I'm trying to find are hard to find through a debugger as it misses the command I want to catch when stepping through each command to find it. I would like to suggest the features "Find out what accesses this address" and "Find out what writes to this address" (the features that are also on Cheat Engine) to be added for Dolphin's debug feature so that it will find what is accessing or writing the code and make those offsets easier to find.

[skid]

I think the debugger already has this feature. It is in the Breakpoints window where a "log" breakpoint can be created. In the log configuration, select "MI Memmap" and "Info" verbosity. The addresses should then appear in the Log window.

[Brandondorf9999]

Where is the log stored at? Also, there are possibilities that the breakpoint will miss that address offset and won't break.

[skid]

In the debugger, use the View > Show Log menu item. You can log it to a file, under User/Logs/dolphin.log

Missing breakpoints should be fixed in the very latest development version of Dolphin.

Alternatively, try swapping between virtual and physical addresses. Change the prefix of the address, 0x80000000 to 0x00000000 or 0x90000000 to 0x10000000.

[Brandondorf9999]

I tried those for some addresses, but those don't work for some addresses. As for the log, I can't find that option in the breakpoints window. I think there needs to be an enhanced feature that will do this when it breaks and then resumes. The function of that will show the addresses during compare, call and jump commands like cheat engine does. Also, how do I make cheat engine work on Dolphin?