Search Issue Tracker
By Design
Votes
0
Found in
5.6.3f1
Issue ID
986857
Regression
No
[IL2CPP] Incorrect stack trace is being returned when logging an error with Debug.LogError()
To reproduce:
1. Open user's attached project
2. Open "scene" and hit play
-- Notice that errors are being logged into the console with this stack trace:
UnityEngine.Debug:LogError(Object)
debugview:ShowTimeInLog() (at Assets/debugview.cs:16)
debugview:Update() (at Assets/debugview.cs:25)
3. Build this scene to iOS (IL2CPP backend) and play on the device
4. Inspect Xcode's console and notice this stack trace:
UnityEngine.DebugLogHandler:LogFormat(LogType, Object, String, Object[])
UnityEngine.Logger:Log(LogType, Object)
UnityEngine.Debug:LogError(Object)
debugview:Start()
Expected result: Xcode's stack trace should match the stack trace from the Editor because Editor's one shows the correct information.
Reproduced with: Unity 5.6.5p1, 2017.3.1p1, 2018.1.0b7, 2018.2.0a1
Device: iPhone 7+ iOS 10.3.2
No repro with Mono backend.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Mobile] Developer Console does not appear when an error is thrown
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- NullReferenceException is thrown when changing the Inspector preview selection
Add comment