In our of our plug-ins that we’re developing and distributing internally (for Rhino 7), we’ve been noticing a recent uptick in Rhino crashes. In these scenarios, a stack trace is a godsend for tracking it down, and we’ve instructed our users to send in a crash report to McNeel every time they experience one, even though we’re pretty sure it is our plug-in’s code that (directly or indirectly) causes the crash. The McNeel devs have been amazingly helpful in pointing us in the right direction from information gleaned from internal crash reports, but problems persist, and we’d like to be able to help ourselves with a quicker feedback loop without bothering you unless there’s an actual issue on the Rhino side – which leads to my request:
Is there a way for us to be able to (locally) access the stack trace from the crash? e.g. could users, along with “Send to McNeel”, also be given a button of “save report to file” or something of this nature in the crash report dialog? Or, alternatively, have it written automatically to some file on their local system? If not, is this something that could be added to a future version of Rhino 8?