DBG_PRINTEXCEPTION_C shouldn't be fatal on windows
That exception is used to send messages to an attached debugger, something like printing to STDERR. Some libraries use it to print status messages during normal operation, so it would be nice if it wasn't an ERROR.
Ideally, there should be some way to see the error message, since a library might use it to print information before signalling a real exception, or the status messages might be interesting.
Attached patch (against 220.127.116.11-2f571fe) WARNs the message, not sure if that is the best way to handle it or not, probably should at least use a specific warning type. Also not sure if just returning NIL from HANDLE-