JosJuice 7cecb28bdf DolphinQt: Properly lock CPU before accessing emulated memory ... This fixes a problem I was having where using frame advance with the debugger open would frequently cause panic alerts about invalid addresses due to the CPU thread changing MSR.DR while the host thread was trying to access memory. To aid in tracking down all the places where we weren't properly locking the CPU, I've created a new type (in Core.h) that you have to pass as a reference or pointer to functions that require running as the CPU thread.		2023-02-12 11:27:50 +01:00
..
CodeTrace.cpp	DolphinQt: Properly lock CPU before accessing emulated memory	2023-02-12 11:27:50 +01:00
CodeTrace.h	DolphinQt: Properly lock CPU before accessing emulated memory	2023-02-12 11:27:50 +01:00
MemoryPatches.cpp	DolphinQt: Properly lock CPU before accessing emulated memory	2023-02-12 11:27:50 +01:00
MemoryPatches.h	DolphinQt: Properly lock CPU before accessing emulated memory	2023-02-12 11:27:50 +01:00
Threads.h	DolphinQt: Properly lock CPU before accessing emulated memory	2023-02-12 11:27:50 +01:00
Watches.cpp	Core: add locked state to watches	2022-12-23 11:59:23 -06:00
Watches.h	Core: add locked state to watches	2022-12-23 11:59:23 -06:00