Yeah, it's possible to know which DLL has raised the exception and include that in the error report. This is something that can be coded in - I've done it for other applications. The minidump Sonar produces probably contains this information, but unfortunately it's not shown to the user, so they can't adjust their usage patterns based on it unfortunately. With this information, avoiding and pin-pointing dodgy plugins would become a lot easier.
 
Regarding 32-bit/64-bit, I know about all that (though no doubt that information may help others). I've seen enough 'Teleport Server has stopped working' messages to last me a lifetime. Giving up all 32-bit plugins is not going to happen unfortunately but I'll be avoiding them where I can, and that included this session.
 
In fact, it would be great to have a 'Safe Mode' that treats VSTs a bit like browsers treat their plugins, ie. by running each of them in a separate process, which makes it even easier to catch when one of them crashes. This would be done by basically running something like Bitbridge for all plugins, not just for those compiled for a different architecture.
 
(Incidentally I had to try about 15 times to post this message... does anyone else ever get repeated 'unexpected error' messages after a 30 second time-out?)

Kylotan
(Incidentally I had to try about 15 times to post this message... does anyone else ever get repeated 'unexpected error' messages after a 30 second time-out?)

Yup quite of lot of them today... cheers...

.. And I would love to see in built diagnostics and performance stats in Sonar of some sort. Maybe even sandboxing. It would slow the DAW down of course so it would have to be an option in preferences. I'd be surprised if this isn't happening to some minor extent already so QA can test.. And then stripped for the final build.

I expect much of the sonar codebase is too old to enable the modern error handling we've become used to...
Greetings from rainy Wales x

I expect much of the sonar codebase is too old to enable the modern error handling we've become used to...
Greetings from rainy Wales x

Not at all. Modern error handling has hardly changed in years. BTW code really doesn't date, program languages do. As C++ is probably still the most popular language nowadays, Sonar is completely fine in that respect. Code efficiency and performance is another matter, as nobody has seen the Sonar source code, nobody here is qualified to comment except Cakewalk about this. Actually coding the error handling is quite simple, the difficult bit is where to put it and persuading developers to do a mundane task.

Try catch can be expensive.

gswitz
Try catch can be expensive.

Right that's why you would have a debug mode in preferences...

You also don't catch crashes with C++ try/catch blocks.

Hmmm trying to.... throw... us  ... ;)