Currently, there is no way to view a detailed log/traceback of what happened when a CTD (crash to desktop) occurs. Especially in the context of development, being able to see which gauge/function/call resulted in the CTD, whether directly or indirectly, is extremely valuable and will save countless man-hours of debugging, especially when it's not even clear whether it could be an issue caused by a module in development, or the sim itself.