assertion failures are called exceptions

[jeffythedragonslayer]

VSCode can give the misleading impression that a C++ exception has been thrown, when really all that happened was an assertion failure when using the assert() function. The call stack also says "PAUSED ON EXCEPTION" (If I recall correctly Visual Studio says "Debug Assertion Failed!")

[WardenGnaw]

The "Exception has occurred" is expected if the debugger receives a stopped event and we can not map it to a breakpoint. If the assertion is giving us a specific exception type we could modify the message to say an assertion has been hit.

To further investigate, are you debugging with type cppdbg or cppvsdbg. Also which assertion library are you using?

[jeffythedragonslayer]

My launch.json has the line "type": "cppdbg" but if I I change it to cppvsdbg I get "convertToDto unexpected type" message box. (A notification saying it's not available on non-windows machines also appears)

This is just the standard C assert from #include

[jeffythedragonslayer]

Segfaults are also called exceptions.

[jeffythedragonslayer]

Sorry, did not mean to close this issue.