reversing C++ and JIT code
Reversing game code involves differentiating between old C++ and JIT-compiled scripting languages, which can be challenging, especially with complex bugs.
- Reading functions is less difficult than figuring out classes and their methods, with Just-In-Time (JIT) compilation being a major challenge.
- Uncovering what's happening is harder when the game code mixes 20-year-old C++ and a custom JIT-compiled scripting language.
- It is possible to differentiate between the C++ and JIT code in memory using decompiled executables and tracking the execution pointer.
- A specific bug involved a valid JIT-compiled script calling a C++ function with corrupted object pointers, leading to game state corruption.
- Ghidra is a suitable tool for this type of reverse engineering, despite some members experiencing errors.


