The most likely anomaly of 0X7C92E4DF in Xx.exe

The most likely exception for 0X7C92E4DF in Xx.exe: 0xc0000008:an Invalid handle was specified

Today I met a very strange problem, yesterday is a good program, today with VS open, in the closing of the main window when unexpectedly pop-up error prompts: Xx.exe 0X7C92E4DF in the most likely exception: "0xc0000008:an Invalid handle was Specified ". At that time all depressed, you say strange strange, what code has not changed, just clean up the solution only, not well! Then, think about the following code problems in the Mainform_formclosing event:

After careful examination, no unusual problems were found. Just after debugging to the WndProc function, the program appears with an error message.

Filled with joy to think that found the problem, but there is no hint of information, at that time it was impossible to do. Not only this, very strange is, obviously I have terminated the program, but again to start debugging but not, ran into the process of a look, has inexplicable wonderful have a similar program running, want to terminate it also not. Finally, turn vs. , then look at the process, no more. I'm depressed again, what's the situation?

More Wonderful content: http://www.bianceng.cnhttp://www.bianceng.cn/Programming/net/

"Our project is the interface of C #, C + + to do the bottom, call a lot of dynamic link library, will not call the dynamic library problem", the head is just a flash, but immediately dismissed the idea. "Because the program was off work yesterday. In fact, the program that you do, I was particularly aware of the problem of the procedure. I believed it was not a problem of the program, it could have been something else.

Oneself to tinker for a while no fruit, ask leader help to see (have nearly ten years programming experience, I quite admire a person), I will simply describe it:

The first problem is in the WndProc function, debugging failed, so we use Spy + + to capture the message source, toss for a while is also fruitless. Because, you can't see any hint at all, any code that might cause an exception. There is no clue. Plus the process is not shut down the program. We are more convinced that it is not a code problem So I try to use the release version of the code, start the shutdown program is not a problem. It seems that the problem is when debugging code. But what problems can occur during debugging? There is no clue, so leader said that the code sent to him, he was on his computer, the perfect operation, there is no problem. This is a good idea. At least you can judge the problem is not the code. But what is the cause of it? First from the computer, and then to the software installed today, the irrelevant software off the uninstall ... Wait, we've all tried. The problem is still unresolved, I'm going to have to reload the system. Catch the noon meal, also no longer think about this problem. A work in the afternoon, Google, see also have similar problems, but are some unresolved, but there is a C/s + + to give me a hint, I took a screenshot of my useful text as follows:

Although the problem is not the same, but it is likely that my program calls the other DLLs, so I wrote with leader A can see the running process of the program called which DLLs, open a normal program, open a debugging problems in the program, compare them, found that the problem of the program than the normal program calls more than 4 DLLs, excluding the system dynamic library, and this program calls the dynamic library, found that more than 4 dynamic libraries, incredibly other programs, MMD, finally found the problem, and then with dependency Walker looked at what functions were called in these dynamic libraries and found that there was a dbgpint function, which was used for debugging.

Decisively uninstall the associated software, solve the problem. Thank leader.