Debugger error

[bobonwhidbey]

I've created a terrible bug in my program. It seems to be intermittent. I can not trace to the offending line. Once the program hangs - it can't be closed with the upper right [X] in Windows, but I can stop Laz (Ctrl-F2).
See attached error message that I've never seen before. I also get a "Windows Security" warning in the lower right of my screen shortly after getting the Debugger error message.

I've tried Dwarf 3 and also Dwaft-2 with sets. Anyone have an idea what's going on here? I'm not looking for help debugging my program but a clue as to what kind of error could trigger that error message.

[440bx]

What happens when you start the process from the command line ? (IOW, no debugger involved.)

[Martin_fr]

If you got a Windows security warning, check if the exe still exists.

I have seen that a few times, that Windows defender deletes the freshly compiled exe, before it can be debugged.  Especially (but not only) when the exe has been recompiled several times in a short time => Windows sees the accumulated changes of the exe (caused by recompiling it) as "evasive action".

And yes, I am 100% sure that in the cases I observed it was a clean exe and no virus was involved anywhere on the system. I restored the exe, and send to virustotal and https://metadefender.opswat.com/ => both reported 100% clean.

Try to exclude the folder from Windowsdefender https://support.microsoft.com/en-us/windows/add-an-exclusion-to-windows-security-811816c0-4dfd-af4a-47e4-c301afe13b26

 

[bobonwhidbey]

Turning off Windows Virus and threat security eliminated the 'Debugger error' and also, of course, the Windows Security message. At least I can now get further into the process of tracking down this bug.

Both the exe and the dbg files exist in the expected folder with the expected time and size.

Thank you Martin for telling me about the ability to exclude just one folder from virus scanning. I feel a lot better about just one folder than the entire PC being "unprotected". When I excluded just the folder with the "offending" files - no error message - although my bug is of course still there.