Open burner opened 1 year ago
Maybe you switched to building 64-bit processes in the mean time? If built with dmd, this uses a custom exception handling mechanism unknown to the VS debugger.
With 32-bit processes and with LDC, exception are regular Win32/C++ exceptions, and can be set to break on throwing exceptions (enable all exception to see which one triggers).
The D-Exceptions only work when using the mago-debug-engine. This can only be selected with visualdproj projects as the debugger to use, but has become obsolete in all other aspects.
laszloszeremi reported this on 2023-04-16T20:00:46Z
Transfered from https://issues.dlang.org/show_bug.cgi?id=23843
CC List
Description
Previously I was able to set Visual Studio to break on user-handled exceptions, however this no longer the case. I have selected it in the Exception Settings, and only affects unhandled ones in my experience. This made the previous habit of mine of checking unittests in a debugger more difficult, as AssertErrors in unittests already handled.