RemedyBG»Forums
Aidan
12 posts
Corrupt function pointers aren't handled correctly
Edited by Aidan on Reason: Initial post
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:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
typedef void MyTestFunction();

int main()
{
    MyTestFunction* myFunc = (MyTestFunction*)0x0BADF00D;

    // Should break into the debugger here
    myFunc();

    return 0;
}
265 posts / 1 project
None
Corrupt function pointers aren't handled correctly
Thanks Aiden. I can take a look.