not sure if it’s bug or just missing feature but in Mono i was able to see line numbers in stack trace correctly. Now with IL2CPP i see stack trace but not line numbers:
Platform is Android and it’s release version so not development build. Happened when we had to change scripting backend from Mono to IL2CPP (for ARM64 as Mono doesn’t support it) and now I see only those zeroes instead of line numbers where on Mono there were line numbers.
We do not currently support line numbers in Release builds for IL2CPP (I’m surprised they worked for you while you were using Mono). We have plans to add Release build support for line numbers in IL2CPP builds in the coming months.
Should this work for iOS builds as well? I’m currently missing line numbers on an iOS build exception, and I have Development Build and Script Debugging checked, and “Run in Xcode as” is set to Debug – the profiler options and “Wait For Managed Debugger” and “Scripts Only Build” are all unchecked, but it doesn’t seem like any of them should be necessary. I’m running Unity 2019.3.5f1
Thanks for any help – would be really nice to have line numbers
Thank you for the info, this would be so useful! I’m a newbie and I really don’t know how to understand which instructions caused an exception in a method. Is there another way in case I cannot repoduce the problem inmy environment?
I understand that it can be tricky at first looking at stack traces to try to diagnose the issue. There are a lot of Unity forums for different areas. If you’re developing for a specific platform and seeing errors or exceptions from then, then I’d try posting the stack trace in the corresponding forum for those platforms. The people there can give you a good starting point on where to look into why you’re running into that issue. I hope this was helpful!
Hi @waldgeist , still no updates at this time. Cloud Diagnostics has been in maintenance mode for the past few months so active development has stalled during that time.
However, we are in the process of increasing head count for this team so that we can resume development of the service. We should hopefully have more updates soon, but I’m afraid I can’t give a timeframe on that response at this time.
Alright, thanks for the info. Just for clarity: I was not referring to Cloud Diagnostics, but to plain vanilla Unity on mobile devices. No line numbers there either.
This is probably my no.1 pain point in using unity that I would love unity to work on as a focus, having a line numbers shown while debugging on il2cpp builds would eventually helps us developer make a better product, is there any information on the progress for this? is it being worked on are is still on your backlogs?
More people should be demanding this as debugging without a proper line numbers is hell
Note that in Unity 2020.2, with the latest release, C# source code line numbers do exist for IL2CPP in stack traces when the managed debugger is enabled.
question for @JoshPeterson while it would work on managed debugger, it won’t show anything for errors captured by tools like crashlytics right? e.g the typical use case we had if this is working is… usually qa report a bug, with a detailed repro steps and error calltack with the correct line numbers so dev could easily fix the error
That is correct. This is only a feature for local development use at the moment. It is possible that we could add support for offline managed call stack symbolication, but we have not done that yet.
