DBG_PRINTEXCEPTION_C shouldn't be fatal on windows

Bug #1437947 reported by 3b on 2015-03-29
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
SBCL
Undecided
Unassigned

Bug Description

Currently DBG_PRINTEXCEPTION_C (#x40010006) just gives the generic "An exception occurred ..." error, and doesn't allow continuing.

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 1.2.9.49-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-WIN32-EXCEPTION is correct, but it seems to work.

Stas Boukarev (stassats) wrote :

In b4bf26582ac92e6270ded439e23957822dffc4b1, slightly modified.

Changed in sbcl:
status: New → Fix Committed
3b (00003b) wrote :

modified patch dropped the "~a" argument to WARN, so it breaks when the message contains #\~ characters (at best changing the message, usually erroring in FORMAT)

Changed in sbcl:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers