View previous topic :: View next topic |
Author |
Message |
Xblade Of Heaven Master Cheater Reputation: 0
Joined: 16 Oct 2005 Posts: 394 Location: DEAD
|
Posted: Sun Jan 28, 2018 8:23 am Post subject: problem on raiseexception |
|
|
Hi all, when i try set a BP on RaiseException game install freeze and me cant see nothing on ce debug info, someone can help me why this happen?
regards
_________________
Welcome to the Hell.
|
|
Back to top |
|
|
OldCheatEngineUser Whateven rank Reputation: 20
Joined: 01 Feb 2016 Posts: 1587
|
Posted: Sun Jan 28, 2018 9:34 am Post subject: |
|
|
what type of exception? and what was your action?
im not sure if CE have exception handling, but i would goto olly and see whats causing this.
for sure i dont know the reason of the exception, but if its was cause by using windows debugger then use veh.
if its olly then couple popular plugins will solve that.
i think you might wanna share some info.
_________________
About Me;
I Use CE Since Version 1.X, And Still Learning How To Use It Well!
Jul 26, 2020
STN wrote: | i am a sweetheart. |
|
|
Back to top |
|
|
Xblade Of Heaven Master Cheater Reputation: 0
Joined: 16 Oct 2005 Posts: 394 Location: DEAD
|
Posted: Sun Jan 28, 2018 10:11 am Post subject: |
|
|
Yes, the purpose of this is to see where the game calls when you enter a breakpoint, just after pressing the escape key the game crash, so you could see where you call before breaking the game, sometimes it worked, but now It does not work and I do not know why. I am using VEH, with the windows debugger it is not possible.
with xdbg64 I could see where it calls to crash the game once you press the escape key, but I do not know why with CE now I can not, before I always did with CE, but now there is no way
_________________
Welcome to the Hell.
|
|
Back to top |
|
|
OldCheatEngineUser Whateven rank Reputation: 20
Joined: 01 Feb 2016 Posts: 1587
|
Posted: Sun Jan 28, 2018 12:21 pm Post subject: |
|
|
honestly i wouldnt recommend doing all this with CE, so either x64dbg or ollydbg. (immunity is better than x64)
also NOPing that call (to ntdll.dll) might cause other issues. (if im not wrong then the process expecting a return value in eax (some specific functions return in ebx, but most likely in eax) or a terminate)
(see if you can reverse the Jcc instructions before that call)
see if you can pass the exception handling to olly or x64. (and give olly or x64 the range of 00000000 to FFFFFFFF for exceptions)
sidenote:
probably it will jump to the raise exception function, once it do that there is no return and ebp will be xor'ed.
_________________
About Me;
I Use CE Since Version 1.X, And Still Learning How To Use It Well!
Jul 26, 2020
STN wrote: | i am a sweetheart. |
|
|
Back to top |
|
|
|