This, apparently throws a debugger into convulsions. Note the INT3 call in there, that's a software break point, in the middle of a routine. To the 'trained' eye, it is instantly obvious what tosses the game. 8D85 BCFDFFFF LEA EAX,DWORD PTR SS:Ġ0D2C259 |.

In OllyDbg, locate the following bit of code (0xD2C253 on my version):Ġ0D2C253 |.

The first detonation in the debugger happens within 'saintsrowthethird-dx11.exe' (note, this is only tested on that specific executable) however. In short, you want an actual string name for your thread, you must raise a specific exception (literally a call to the 'kernel32.RaiseException' (which under Win7 calls KERNELBASE.RaiseException) function) to do so.īinkw32.dll seems to do just this, but only if a debugger is present. idiots) if you want to assign a NAME to a THREAD. I decided to track this down, since the error message (the second one actually, the first 'bomb' was quickly found) it throws DURING the replay of the intro movie uses an 'error code' that isn't actually and error code but an exception one MUST raise (yeah, MS, that's how it's done. So, I picked Saints Row the Third, which I had just purchased for a nice price.Īfter the necessary 'installation' of a crack (don't want to screw up my Steam account, even if it is improbable), I think its a Skidrow one, I noticed that when the game is launched in a debugger (open process in CE, start it in OllyDbg, etc), it bombs out in a rather 'cute' manner. I needed something to test a plugin I coded for CE. Posted: Wed 11:41 pm Post subject: Saints Row The Third + start in debugger lollygagging.

Saints row 2 cheat engine