Qt Creator uses Microsoft debugger, C: Program Files (x86)\Windows Kits\8.1\Debuggers\x86\cdb.exe
Error if found:
Exception at 0x7715c5af, code: 0xe06d7363: C++ exception, flags=0x1 (execution cannot be continued) (first chance) in dwrite! DWriteCreateFactory
or
:-1: error: Debugger encountered an exception: Exception at 0x7fefcecb87d, code: 0x4242420: , flags=0x0 (first chance)
Find information online from blog.sina.com.cn/s/blog_93fa… To learn that:
When running a program in a debugger, if the program raises an exception, the debugger is notified First (that is, a first-chance exception), which is then caught by the program that created it. If the program does not catch this exception, the debugger is notified again (i.e., second-chance exception, last-chance exception) and terminates the program. A first-chance exception is 0xC0000005: Access Violation, 0xC00000FD: Stack Overflow, etc. All of these indicate that there is a defect in the program that needs to be fixed. However, some exceptions are normal, for example, first-chance exception in xxx.exe (kernel32.dll): 0xE06D7363: Microsoft C++ exception. Structured exceptions (SEH) are widely used in The Windows operating system to handle special cases, and many apis that deal with the underlying environment rely on SEH to handle possible contingencies. Also, these apis have code that captures SEH, and the resulting exceptions do not affect the program. But because of the “first-chance exception, second-chance exception” mechanism mentioned above, VC will still have output, but we can completely ignore it. If you really don’t like the output, you must disable “first-chance exception” catching for certain exceptions.
As shown in the figure, remove the check box.
