Currently, it is very difficult to debug crashes with CUBOS_FAIL without using some debugger to view the stack trace.
This is a big problem considering that if a deployed game crashes, we won't be able to figure out what happened.
Solution
We should make it print a stack trace, somehow.
There are platform specific ways to do this, which we can resort to if we want to avoid including a library.
Problem
Currently, it is very difficult to debug crashes with CUBOS_FAIL without using some debugger to view the stack trace. This is a big problem considering that if a deployed game crashes, we won't be able to figure out what happened.
Solution
We should make it print a stack trace, somehow. There are platform specific ways to do this, which we can resort to if we want to avoid including a library.
The best option is probably to just use cpptrace.