Of course its possible but this is what one does when "real debugging" is not available. As for the text debugging using the log. MonoDevelop lets you use breakpoints and preprocessor macros just as well as any other IDE. A "CLR" focused on rendering games in many platforms and not the classic C# CLR. Machine The name of the computer or device that this instance of Unity is running on. Project The name of the Unity project that's running in this instance of Unity. The Select Unity Instance dialog displays some information about each Unity instance that you can connect to. So, the "CLR" you are programming in Unity is actually the unity engine itself. In Visual Studio, on the main menu, choose Debug > Attach Unity Debugger. The whole misunderstanding in my opinion, is caused by the fact that the language that Unity is using, is not exactly C#, but a unity-variant that looks like C# and it may be compatible with C# but I do not know to what degree. Even if, it is pure Common Language, which I seriously doubt because if it was pure CL there would be no need for a separate (potentially customized) CLR to be including in the engine. Lastly, there are stuff like the threads of the program that are not open sourced, so I doubt that any external tool would be able to find its way around the code. Unity is built around the editor anyway! For instance, within the editor context, you can change public variables and references while playing the game, which is not a "classic" programming approach. They do describe ways to do that but, I think its safer and easier to use the Unity Editor. NET CLR but a separate (potentially modified) CLR embedded to the engine. This means that most of the time, if the variables and methods are not replaced by gibberish (which is called obfuscating), the program can be read directly by a debugger attached to the executable.Īccording to the conversation, the unity engine does not use the. This intermediate language is not executed by the CPU directly but by a virtual machine instantiated once per application or process, which is called the CLR (Common Language Runtime). NET languages like VB.NET, C#.NET and C++.NET.
In the case of C# this intermediate language is call Common Language (because it is common for all.
Contrary to C for instance that produces machine code, executed directly by the CPU.
C# produces an intermediate language when compiled. Some quick notes for someone not versed in virtual machine languages. There is an open conversation about how this can be done here: in C# there is no need for debugging symbols for the attached debugger to see the code and it runs over a virtual machine. That way you can launch debugging sessions without using an IDE. I think that what the question is after, is a way to launch a "unity built game executable" and attach the debugger to it.Ĭreating debugging symbols with gcc, building the application with DEBUG enabled and launching the executable program with gdb to debug it.
0 kommentar(er)
