Version: 2020.3
Windows Runtime support
Scripting restrictions

Managed stack traces with IL2CPP

When an exception happens in managed code, the stack trace for the exception can help you understand the cause of the exception. However, the managed stack trace might not appear as expected in some cases, as explained below. The stack trace varies depending on the build configuration. ​

Debug builds

When you use the debug build configuration, IL2CPPA Unity-developed scripting back-end which you can use as an alternative to Mono when building projects for some platforms. More info
See in Glossary
reports a reliable managed stack trace, and includes each managed method in the call stack. The stack trace does not include line numbers from the original C# source code. ​

Release builds

When you use a release build configuration, 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. This is the method where the exception occurred. It also includes other methods if they are not inlined. ​

Source code line numbers

IL2CPP call stacks do not include source code line number information in the debug or release configurations.

Windows Runtime support
Scripting restrictions