A while ago, I added a mechanism to the game that would cause it to crash if an uncaught exception was thrown. Later, another contributor made it configurable, and off by default.
While I can understand making it configurable, I don't think it should be configurable by the end-user; only by the application, and it should also be on by default. If an error isn't caught, it means that some problem has occurred that the application is unprepared to deal with, and with many applications, crashing is the only useful way of communicating that to the end-user. We could also have a crash screen, that would basically show the crash report and allow it to be copied to the clipboard.
Another thing, should crashing skip the normal shutdown sequence? I've found a number of cases where the game would freeze because it tried to crash while shutting down.
Similar arguments can be made for catching exceptions in the update loop and gamepad support.
Thoughts on any of these ideas?