IL2CPP로 관리되는 스택 추적

When an exception happens in managed code, the stack trace for the exception can help you understand the cause of the exception. This can often be found in the player log file. However, the managed stack trace might not appear the way you expect because the stack trace varies depending on the build configuration.​ ​

C++ Compiler Configuration options

Debug

When the C++ Compiler Configuration is set to Debug, IL2CPP reports a reliable managed stack trace, and includes each managed method in the call stack. The stack trace doesn’t include line numbers from the original C# source code. ​

Release and master

When the C++ Compiler Configuration is set to Release or Master, IL2CPP might produce a call stack that’s missing one or more managed methods. This is because the C++ compiler has inlined the missing methods. Method inlining is usually good for performance at run time, but it can make call stacks more difficult to understand. IL2CPP always provides at least one managed method on the call stack. For stack traces created from managed exceptions, this is the method where the exception occurred. It also includes other methods if they aren’t inlined.​ ​

소스 코드 줄 번호

To locate errors that the compiler finds in your code, you can configure the managed stack trace information to include the file name and line number in the managed stack traces. The managed stack trace information does not include this information by default, because it increases code size and causes the Unity Player to run more slowly.

Note: The option to include line numbers in the stack trace is only available on desktop platforms.

To configure the managed stack trace information to include the file name and line numbers:

1. Go to Edit > Project Settings > Player > Other Settings.
2. Set IL2CPP Stacktrace Information to Method Name, File Name, and Line Number.

Note: When the C++ Compiler Configuration is set to Release or Master, you might experience the following:

• The compiler might inline some functions, which causes them not to appear in the stack trace.
• The source code line numbers might not match up with the correct line numbers in your code.

Script Debugging enabled

To enable Script Debugging, go to File > Build Settings then click the checkbox next to Script Debugging. With Script Debugging enabled, IL2CPP will always report a correct managed stack trace with the method, file name, and line number. However, this increases the program size and produces slower code. Using script debugging solely to improve stack traces is not recommended. Instead, enable the option shown above.