Cheat Engine

[drdorianwhite]

I'm novice to ce but wondering if I even need to use Olly anymore for reversing for games if ce has all the features i need.

I'm trying to locate the call stack in the debugger. Where is this located?

[Dark Byte]

when single stepping in the bottom right of memoryview (right of the hexview). Rightclick for different kind of views (normal stacktrace, dword view, modules only)

When using stuff like find what accesses the S button will show the stack at the time of the capture

[drdorianwhite]

I basically wanted to know what is the easiest way to trace backwards through the call stack...for instance, I used the "find what accesses" to get a an instruction im interested in. I then want to know where the register gets its value. the register is getting it from the ECX register early on, from fastcall convention, so I want to go to the higher level function to see how that value is passed and where it came from originally.

So, I guess I just want to know, how can I step out or upwards?

[Dark Byte]

The default stacktrace view, the first line is what called the function you are in

Alternatvely, if you're on 32-bit and use kernelmode debug you can enable the last branch recording feature with lua and on breakpoint call the functions that show you the jumps and calls that lead it to the breakpoint (min 4, max 16 depending on cpu)

[Geri]

There are many ways to find the calling function in CE.

Manual debugging:
1. Look at stackview.
2. Use Execute till return... (Shift+F while debugging.

Auto debugging:
1. Press on the S button to view the stack.
2. Use break and trace and check in the tree where is the debugged function returning.

And there was more in my head but now I forgot all the possibilities. Anyway there are more solutions as you see.