![]() |
|
Memory breakpoints don't always work - Printable Version +- Dolphin, the GameCube and Wii emulator - Forums (https://forums.dolphin-emu.org) +-- Forum: Dolphin Emulator Discussion and Support (https://forums.dolphin-emu.org/Forum-dolphin-emulator-discussion-and-support) +--- Forum: General Discussion (https://forums.dolphin-emu.org/Forum-general-discussion) +--- Thread: Memory breakpoints don't always work (/Thread-memory-breakpoints-don-t-always-work) |
Memory breakpoints don't always work - oPryzeLP - 12-12-2015 Depending on the address, memory breakpoints will sometimes not work at all. The value in question I can see changes every frame, yet no break is called. Whereas a different address may work every single time. Why is that? Is there a workaround? RE: Memory breakpoints don't always work - skid - 12-13-2015 It depends on what changes the memory and whether the address is virtual or physical. Addresses starting with 0x8XXXXXXX or 0x9XXXXXXX (virtual addresses) will work if the data is changed by the CPU. If another hardware device is writing the data (e.g. a DMA transfer from the disc interface), the change might not get picked up by the debugger. In these cases, a physical address might work. Physical addresses start with 0x0XXXXXXX or 0x1XXXXXXX. To swap between a physical and virtual address, change 0x8 to 0x0 and 0x9 to 0x1 (or vice versa). RE: Memory breakpoints don't always work - oPryzeLP - 12-13-2015 Thanks you so much! It works! You're a lifesaver!
|