Cheat Engine

Geri · Moderator Reputation: 111 Joined: 05 Feb 2010 Posts: 5636

Hi DB!

I am assuming that when I use the trace, the slowdown of the program is mainly caused by the logging, and not by the tracing itself. So in theory the trace could be speed up if I would use some filter to not log all instructions, only those that are important for me.

Am I able to specify somehow (in lua or otherwise) to log specific instructions only? Like log only call and ret instructions or only cmp or jump instructions. Would this grant enough speed to be able to work with the target process while the debugger is running and tracing those instructions?

Thanks!

Dark Byte · Posted: Tue Feb 01, 2011 9:15 pm Post subject:

nope, actually stepping through will slow it down to a crawl.
Just tested it with this script: (Won't work in ce 6.0 because of a bug where the continue option is not properly set: bypass, do at least one single step and then run the script and do another single step yourself)

Geri · Moderator Reputation: 111 Joined: 05 Feb 2010 Posts: 5636

Thanks. I was thinking that filtering the logging may actually speed up the debugging process. Usually I just look for specific things like function entry points, jumps and other interesting things so the rest of the instructions are kinda useless for me anyway in 90% of the cases. I was thinking I could log larger parts of the application not just a few thousands of code lines if I use some filtering, but then I will just stick to a few ten thousands of codes and wait a few minutes for the result. Smile

It is still working like a charm and navigating in functions with the trace tree is a dream. It was one of Your best ideas to implement that feature.