Quantcast
Channel: Comments on: IL2CPP Internals – Debugging tips for generated code
Viewing all articles
Browse latest Browse all 8

By: Morten Nielsen

$
0
0

We noticed that the iOS IL2CPP generated code does not crash our game when e.g. a NullReferenceException is thrown like in the example above:

Important boom = null;
Debug.Log(boom.InstanceIdentifier);

This will simply print the call stack to the console and keep the game running – in a, now, invalid/undefined state due to stack unwinding.

Is there any way to get the game to properly crash when an exception is thrown?

With the old mono runtime (we upgraded from 4.5.5 to 4.6.6p3) we would get a proper crash, which we would then send to HockeyApp.


Viewing all articles
Browse latest Browse all 8

Latest Images

Trending Articles



Latest Images