First-chance exception in kernel32.dll 0xe06d7363 Microsoft C ++ exception

First-chance exception in kernel32.dll 0xe06d7363 Microsoft C ++ Exception2009-05-04

Debug in VCProgram"First-chance exception in xxx.exe..." is sometimes displayed in the output window. In general, this is because an exception occurs in the program and the output is captured by VC.

When running a program in the debugger, if the program has an exception, the debugger will first receive a notification (that is, the first-chance
Exception), and the program that generates the exception is responsible for capturing the exception. If the program does not capture this exception, the debugger will be notified again (that is, second-chance
Exception, last-chance exception), and end the program.

The common "first-chance exception" is generally "0xc0000005: access violation", "0xc00000fd: Stack Overflow", and so on. These indicate that the program has defects and must be corrected.

However, some situations are normal, such as "first-chance exception in
Xxx.exe (kernel32.dll): 0xe06d7363: Microsoft C ++ exception ". Windows
In the operating system, structured exceptions (seh) are widely used to handle special situations. Many APIs dealing with the underlying layer rely on seh to handle possible accidents. In addition, seh is captured in these Apis.
OfCodeThe exceptions will not affect the program. However, due to the "first-chance exception, second-chance
Exception "mechanism, VC still has output, but we can ignore it completely. If you really do not like the output information, you must disable the "first-
Chance exception "capture.

First-chance exception in xx.exe (kernel32.dll): 0xe06d7363: Microsoft C ++ exception

When debugging a program in VC, the output window may sometimes contain information such as "first-chance exception in xxx.exe. In general, this is because an exception occurs in the program and the output is captured by VC.Sometimes there is no error while running the program, but it is always stopped to debug the following program.

Some people say this is a bug in visual itself. It takes a long time to understand it and share my solutions. Thank you first

Http://hi.baidu.com/wytzsjzly/blog/item/8db27122f1bdbbac4723e8c1.htmlAnd

Http://topic.csdn.net/t/20060827/21/4979152.html.

When running a program in the debugger, if the program has an exception, the debugger will first receive a notification (that is, the first-chance
Exception), and the program that generates the exception is responsible for capturing the exception. If the program does not capture this exception, the debugger will be notified again (that is, second-chance
Exception, last-chance exception), and end the program.

The common "first-chance exception" is generally "0xc0000005: access violation", "0xc00000fd: Stack Overflow", and so on. These indicate that the program has defects and must be corrected.

However, some situations are normal, such as "first-chance
Exception in xxx.exe (kernel32.dll): 0xe06d7363: Microsoft C ++
Exception ". Windows
In the operating system, structured exceptions (seh) are widely used to handle special situations. Many APIs dealing with the underlying layer rely on seh to handle possible accidents. In addition, seh is captured in these Apis.
The exception will not affect the program. However, due to the "first-chance exception, second-chance
Exception "mechanism, VC still has output, but we can ignore it completely. If you really do not like the output information, you must disable the "first-
Chance exception "capture.

The method is as follows:

-Start debugging your program.
-Go to debug | exceptions...
-Choose "e06d7363 Microsoft C ++ exception" from the bottom of the "exceptions" list.
-Choose "Stop always"
-Click "change"
-Click "OK"

Now
Your debugger will stop when it encounters
First-chance C ++ exception, and you can examine the call
Stack, etc, and investigate. (You may need to restart
The debugging session, if the exception has taken
Place before you get this setting changed .)

Select "e06d7363 name: Microsoft C ++ exception" in "Number" and select "Stop alwaws" in "action, if you select "stop if not handled", it will not stop here.