-
Notifications
You must be signed in to change notification settings - Fork 38
access violation #18
Comments
Did you called It should be called from within |
@reduf I tried your suggestion but I still receive the same access violation. GW:Scanner:Initialize executes correctly and GW::Initialize throws the exception. |
When the access violation is thrown, can you check the value of g_base and g_size ? |
Sure, pattern | 0x003fafac "V‹ñ;ðr\x4" | const char * |
g_base and g_size are correct, but for the pattern can you post the code at the calling site. That is the |
Sorry to touble you, I'm not really well versed in debugging with visual studio code so I might not be following you correctly. In my call stack I see : It seems the function executed before this exception is thrown is GW::MemoryMgr::Scan In that one, it's this line that's throwing the error but there's no pattern variable here. It's a fixed string. PS: I couldn't find any string in the code called FindPattern. |
I think that the problem is that GWCA only make sense if it's inside |
I was under the impression that I can build my application including GWCA as a library and the initialize function would let it hook itself to the gw.exe instance. |
You can build a dll including GWCA and load this dll into the game process. |
Hi,
I'm trying to include GWCA in my project as in the example and I've added the include libraries in my setup. The executable now builds fine however when I execute the first function GW::Initialize() I receive the following error
Exception thrown at 0x00806823 in App.exe: 0xC0000005: Access violation reading location 0x00401000.
System.AccessViolationException: 'Attempted to read or write protected memory. This is often an indication that other memory is corrupt.'
And it's happening here
So I'm pretty much stuck at the first step.
Any ideas why this might be happening? I'd be happy to provide additional info to troubleshoot it if I new what is needed :)
Any help is appreciated.
PS: I'm running as administrator and with a/v disabled completely.
The text was updated successfully, but these errors were encountered: