Windows IL2CPP and stack traces

Unity Engine
1

Hello

I’m playing around with building for IL2CPP and everything seems to go just fine… until I actually hit an error, well sometimes. In the development console and in the log files it targets the function that an error appeared in but the exact line is another story. I don’t know the exact term but I believe it’s just pointing to a memory address. So how can I decode these stack traces?

I am also using performance reporting (which will be the main target for me to see errors and not log files) and it’s the same story there. I thought I could upload the SymbolMap file that is being created and then it would do something with that, but I was apparently mistaken.

2

Could you please post the stacktrace?

3

We don’t have support for source code line numbers in IL2CPP stack traces. This information will add a good bit of size to the application package, but it might be something we could consider as an optional feature.

Is the debugging information worth a size increase in your case?

4

Definitely useful for a development build. Our QA is testing mostly development builds and having line numbers would make stack-traces, that are attached to a bug-report, way more useful.

EDIT: By the way, you could strip all the “C:/buildslave/unity/build/” paths (keep only the relative path from that location) to reduce memory and make those stack-traces even easier to read.

5

Ok, I’ll see if this is something we can do. No promises yet, but it should be possible.

1 Like
6

This is from just throwing an exception by myself. It’s nothing exciting.

MainMenuManager.Start () (at <00000000000000000000000000000000>:0)

As Peter77 said, it would be really useful when doing beta/test releases. Sometimes IL2CPP brings on a few new problems and when the problems strike on another person’s computer, it might be hard to debug just going from the stack trace given. So an optional feature that includes more detailed stack traces by sacrificing build size would be very awesome!

1 Like