Early breakpoints not detected #1757
Description
Current Behavior
Placing an execution breakpoint on a region of memory which doesn't have a module loaded in it yet will not cause execution to halt later when that region is actually being executed.
Expected Behavior
The cpu should know if it is executing an instruction with a breakpoint on it if it was placed in the past, no matter if there wasn't an instruction there yet when it was placed. This makes it exceedingly annoying to debug RPL modules because the instruction pointer address they produce in crash logs isn't a valid breakpoint address at startup, as you have to place it after the RPL is acquired.
Steps to Reproduce
Place a breakpoint in a memory region where an RPL is going to be loaded, and the CPU will not halt later when that address is populated and executed.
System Info (Optional)
OS: Fedora Linux 43
GPU: RX 7900 GRE
Emulation Settings (Optional)
Single-core interpreter
Logs (Optional)
No response