I'm reverse engineering a Windows application which has a main executable that appears to run some boilerplate/stub code before calling UnityMain and also using Mono. This means that if I use an assembly debugger like x64Dbg, I get stuck in the boilerplate and runtime code. But, if I view the assemblies in dnSpy, it paints an incomplete picture and makes it difficult or impossible to debug the program because the assemblies I'm viewing in dnSpy are just "libraries" and the execution path is initiated from the native code stub which calls UnityMain. What are some strategies to debug code execution of this type of application?

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.