11/29/2022 0 Comments Sleeping dogs hk ship.exe![]() ![]() I attached a screenshot with my settings. That one also doesn't rely on debug registers Could you elaborate on this?Īnd yes, I know the definitive edition doesn't have these issues (afaik, most likely the internal debugger was removed on release) but I prefer the normal edition and that's what I'm trying to hack.Īlso, if your system is compatible, you could try dbvm level debugging. In your last post you said to "patch all the codes that rely on hardware breakpoints and emulate their behaviour". ![]() Drx value assignment but it looks like it crashes just after launching the exe, not even the program window shows. I tried nopping the call instructions to these functions as well as skip the. Now, I decompiled HKShip.exe in Ghidra, and managed to find CALL instructions to "AddVectoredExceptionHandler" as well as setting Dr (Debug registers) memory addresses, screenshots:Ĭhange 0 to o, it does not let me post URLs for some reason ![]() It's true that it does not crash if I deactivate "Override existing breakpoints when setting breakpoints", but then nothing is shown in "Find what." routines, even though it must show since the value is being changed by the game. Sry for urls, it does not let me post them yet Hey, sorry for bumping this old post but I'm having this exact same issue with Sleeping Dogs (the normal edition), looks like the devs left some hardware breakpoints in the game and when I attach the CE VEH debugger, it crashes the game whenever I try to use the "Find what." functionability. With some luck you will have a few seconds before the game crashes, allowing you to find the code that accesses the variable Then in the threadlist select all threads, except the one that triggers the breakpoint almost every second, and then rightclick and choose the option to clear the debug registers Play the game a little and see which breakpoints have been hit and which threads it occurs the most. To increase the odds attach the veh debugger to the game(using the processlist, NOT by setting a breakpoint), and watch mv->view->debug events You can prevent that crash by going to settings->debugger options and disable "override existing breakpoints when setting breakpoints", of course, if the thread that accesses it also has those breakpoints set, you won't find anything. If the DRx values are not set to 0, that means the game makes use of the breakpoints, and if you replace them with your own, those breakpoints never get hit, and thus crash the game. Get the cracked version of the game, not only will debugging be easier, the game will most likely run smoother as well.Īnyhow, to see why it crashes, go to memoryview->threadlist and expand the threads. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |