-
-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix scan_pattern_page read bytes out of range. #112
Conversation
With this patched in, I'm unfortunately still receiving WinApi 299 errors from |
Is your system is x64, and the target process is x86? |
Yes, that is correct. I'm using a 32-bit version of Python 3.11 as well. |
I just read your library code, it is scanning memory directly with But I've tried the 32-bit process on my computer and it doesn't reproduce it, sorry can't help you. |
Yep, it's nothing fancy. Just a class that's wrapping I have a few functions that will run a scan indefinitely. It could work for minutes or hours, but it will eventually throw a 299. No changes to the pattern, but the exception is in my linked mention above. It's not |
Oh, I thought it reported an error on first run. You can ignore this error, as the program may be freeing memory or switching page properties. |
`pymem` is sometimes throwing this error when you're just standing still. There's a [proposed fix](srounet/Pymem#112) upstream that might resolve these. It looks like this issue started (at least for clarity) when I forked over some changes that were made to how bytes were read.
@StarrFox what's your thoughts on this ? |
seems fine to me |
fix #111