This is related to regular assert(...) There are two scenarios that I'm interested to improve in my code. 1) a debug build app is started regularly, if there is an assertion I'm getting "Debug assertion failed" dialog box with "Abort", "Retry", "Ignore". Abort and Ignore answers are working fine. The problem with Retry. If I hit retry I'm getting that useless "Application error, breakpoint has been reached" "OK" - to terminate, "Cancel" - to debug the program. WTF would I see that useless dialog with default focus on "OK", which is to terminate, after I already made decision to debug the program?! Sometimes I just quickly hit space bar and the process is gone, I lost an opportunity to see what was wrong! So, the question here I have: is it possible, to avoid this dialog and directly go to "Just in time debugger" dialog that shows choices for debuggers. I understand that the nasty "Application error" dialog box is triggered by __debugbreak() or _asm int 3 on intel, so after "Retry" was pressed I need t somehow initiate debugger attach without using _asm int 3. Is this possible? I couldn't find any WinAPI that does this
2)a debug build app is started in VS debugger (using F5). If there is an assert triggered I don't want to see any dialogs at all, I want it to stop right on the line where assert is. I managed to install crt debug runtime hooks and if IsDebuggerPresent then I __debugbreak() and it stops on the line of the assert. It works perfectly when I'm debugging windows mobile builds, but I'm still getting useless dialog box for Win32 builds: "APP.exe has triggered a breakpoint", "Break", "Continue", and greyd out "Ignore". What a useless dialog box!! Any way to completely disable it, so I never see it??
thanks