Pymem
Pymem copied to clipboard
srounet
Fix scan_pattern_page read bytes out of range.
With this patched in, I'm unfortunately still receiving WinApi 299 errors from read_bytes.
With this patched in, I'm unfortunately still receiving WinApi 299 errors from
read_bytes.
Is your system is x64, and the target process is x86?
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.
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 pattern_scan_all, there starts with 0 that should be no offset problem, it is probably caused by other places.
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 pattern_scan_all.
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 pattern_scan_all itself, but scan_pattern_page, which is called from above. As it's iterating over the pages, there's one page that trips it up while it's executing read_bytes over the pages.
Yep, it's nothing fancy. Just a class that's wrapping
pattern_scan_all.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
pattern_scan_allitself, butscan_pattern_page, which is called from above. As it's iterating over the pages, there's one page that trips it up while it's executingread_bytesover the pages.
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.
