IL2CPP stack traces

Unity Engine
,
1

Where a build with Mono used to give this stack trace:

UnityEngine.Debug:Log(Object, Object)
Log:Info(Object, Object)
SomeScript:SomeMethod()
OtherScript:OtherMethod()

IL2CPP on iOS gives us:

SomeScript:SomeMethod()
OtherScript:OtherMethod()

Log.Info() is a custom log utility. So it seems like frames with “log” in them are being filtered, which breaks our log utility with IL2CPP in some cases because it was doing its own processing. Can we get a definitive description of how the stack trace is processed in IL2CPP?

2

@utku.u

Stack traces should be the same between IL2CPP and Mono. It is possible that a method is inlined on in the build of the generated C++ code, and so will be missing from the stack trace. This usually only happens with a release build in Xcode though. Do you know if these missing stack frames occur in debug mode in Xcode as well?

Also, what is the Unity build toolchain for this project? We have some limitation for iOS stack trace support that occurs when the Unity editor is used on Windows, but the iOS project is built on OSX (without a Unity installation present).

3

I build the project entirely on OS X. There are no missing stack frames when I build in debug mode in Xcode, so it seems you are right about inlined functions. I guess I’ll need to adapt the log utility for this.