Loader Lock in MFC mixed application

  • Thread starter Thread starter Luis F. Rodas
  • Start date Start date
L

Luis F. Rodas

When I use the debugger in Microsoft Visual Studio 2005 to debug my
Microsoft Foundation Classes (MFC) class library application, I receive an
error message:
"Managed Debugging Assistant 'LoaderLock' has detected a problem in
<filename.exe>. Additional Information: Attempting managed execution inside
OS Loader lock. Do not attempt to run managed code inside a DllMain or image
initialization function since doing so can cause the application to hang."

This problem does not occur when I run the same MFC class library
application outside the debugger.

I found a fix on http://support.microsoft.com/kb/913996/en-us. How do I get
this fix ?

Best Regards,

Luis F.
(Indusoft Team)
 
Luis F. Rodas said:
When I use the debugger in Microsoft Visual Studio 2005 to debug my
Microsoft Foundation Classes (MFC) class library application, I receive an
error message:
"Managed Debugging Assistant 'LoaderLock' has detected a problem in
<filename.exe>. Additional Information: Attempting managed execution
inside OS Loader lock. Do not attempt to run managed code inside a DllMain
or image initialization function since doing so can cause the application
to hang."
Click to expand...

It's a warning, not an error. Why are you running an MFC application with
Managed Debug Assistants? Are you using .NET components so that you need to
compile with /clr? Without /clr the problem does not exist.
This problem does not occur when I run the same MFC class library
application outside the debugger.
Click to expand...

Yes it does, but you do not receive the warning because the check is
disabled.
 
Back
Top