When a function pointer that has been corrupted is called, remedybg doesn't break at the calling point as I would expect. It does display User-mode data execution prevention (DEP) violation
in the top bar, but it doesn't display where in my code the broken call was (in either source or disassembly), like it does when debugging with visual studio.
Here is a minimal repro case:
typedef void MyTestFunction();
MyTestFunction* myFunc = (MyTestFunction*)0x0BADF00D;
// Should break into the debugger here