"Debugger detected-Please close it down and restart !" Problem Solving

Debugger detected-Please close it down and restart !... Blahblahblah

Some people have encountered this problem, and I have also encountered it, but it has not been solved until this time ......

Start from scratch, or the gmfbridge project. I used the gmfplay example to study gmfbridge. Soon after the compilation passed, I started to test the example function, the compiled executable files can be executed normally, so next I naturally think there is no problem with the project and started to execute the files in the IDE of vs2005, after adding the file, the program does not respond, and the "State" is heard. What is the error? A dialog box is also displayed? But I cannot see the dialog box. What is the problem? After a long time, I decided that there was a problem with the gmfbridge bridge. cpp 566 line, which is the following line of code:

HR = pgraph-> render (ppin );

I further found that there was a problem during the second cycle. It was a bit scratched-headed at this time. Why did the error occur during render? I can't track the problem either.

After one night, I thought about dumping my analysis when I encountered an error the next day. I also learned it. I just need to spend more time studying it. So debugdiag (https://www.microsoft.com/downloads/details.aspx? Familyid = warn & displaylang = en & TM) When an error occurs, dump a full dump and mini dump. debugdiag is used for analysis. debugdiag is really good, so it is easy to use, the message "detected possible blocking or leaked critical section at NTDLL!" is displayed! Ldrploaderlock owned by thread 5 ...... "The entry-point function for a dynamic link library (DLL) shocould perform only simple initialization or termination tasks, however this thread (5) is displaying a message box. follow the guidance in the msdn documentation for dllmain to avoid access violations and deadlocks while loading and unloading libraries. ", it indicates that a dialog box is displayed on a background thread, which causes the program to be blocked. However, at this time, it is still unknown, DLL inside how to play the dialog box, so, ask Xiong Li (http://blogs.msdn.com/lixiong/default.aspx), after his prompt, hard scalp his own windbg analysis of the full dump, in fact, there is no imagination in the difficult, after ~ * Kl100 ,~ After the commands 5s, kb100, and DA 02264ed0, da prompts the information in the dialog box. That's right! That is, the first sentence, so I recalled that I had encountered this problem two years ago. I also encountered this prompt when developing a DirectShow-related program, it was just a separate app at that time, so a dialog box was directly popped up. This gmfbridge itself was a DLL, And the dialog box caused a thread block, which caused me to go back to this circle.

I remember that at the time I thought that the pop-up dialog box in render was MS's protection for your DLL to prevent reverse engineering from analyzing it, but this time it was a bit strange, this dialog box is displayed only when the second render is used. If I want to, the dialog box should be displayed for the first time. Why should I wait for the second time? I am a little overwhelmed again.

After a while, I had to focus on Google, hoping to find a satisfactory answer. I searched for two reasons: 5.1 DivX codec and Nero burning rom 6, but these two items were not installed on my machine, is it because I installed a storm video or kmplayer that contains a component of Dongdong? How do I know which component is it? Difficult Not Chengdu unload, but this is not the way ah, I continue to look at a few may be useful posts, one of them (http://www.hitlabnz.org/forum/showthread.php? T = 70) caught my attention. I clicked the second page of the post and the last reply caught my attention:
"
July 30th, 2007
Julian
Member join Date: Nov 2004
Posts: 5

--------------------------------------------------------------------------------

Hello all,

I too have encountered this problem and you do not have to completely uninstall Nero burning Rom to fix this. It is possible to keep most of the functionality of Nero and run artoolkit apps as well.

The problem is that Nero installa DirectShow filter which uses a Protection Scheme (asprotect) to prohibit their code being run in a debugger. It sees Visual Studio as a debugger and kills you application.

As far as I can tell the troublesome filter is nevideo. ax, which you can find in: C: \ Program Files \ common files \ ahead \ dsfilter (assuming default install directories etc ...).

I renamed this file to "nevideo. Ax. Old" and the problem went away.

I haven'tnoticed any CED functionality in Nero burning Rom, although I only do simple CD/DVD burning. if you use any of the multimedia functions of Nero, you might run into problems after renaming its DirectShow filter. perhaps someone cocould try it and report back.

Good luck,
Julian.
"
It is very useful, so please forgive me for putting the full text of my reply here. Thank you, Julian!

The cause is already obvious. It was caused by a DLL with asprotect and shell. I searched for it on my machine without nevideo. which file is the culprit of ax?

Return to the IDE and notice the DLL loaded in the output window. During the second render, the DLL -- trldrp6.ax was loaded. Is it true? How to confirm?

At this time, my poor crack knowledge played a role and found the peid shell check tool. After a look, the truth is clear. Call, finally find the real culprit, it feels really easy.

Let's take a look at this process, involving dump files, windbg debugging, DirectShow, and shelling tools. It's really not easy and Lucky. Julian's reply was made in July 30, it's just more than a month. It's just a short time!

Put your experience here, hoping to help you. Pai_^