DCoder
03.11.2008, 17:45:32
Actually, this is not a reproducible EIP - the topmost stack dword is one of the EIPs that can cause this. The EIP reported is a (no longer valid) pointer to a function pointer stored in dynamically allocated data, which will most certainly vary all the time. I didn't say this was definitely caused by the harvester, just that it seems like a reasonable cause. There are of course other reasonable causes, such as whatever was erasing other infantry right at that moment or immediately before.