How Do I Run in Debug Mode in VS2005? (1 Viewer)

[cwbynum]

I am able to compile and run the compiled release, but I can compile and run in Debug to trace through the code. It does compile in Debug, but I get a lot of errors trying to run it. I have copied the Skin and Language folders from the Release folder to the Debug folder. I just need help getting started here. The Debug folder is full of stuff including another solution file. Here are some of the errrors I get when running in Debug as I choose "Continue"

Managed Debugging Assistant 'LoaderLock' has detected a problem in 'D:\Projects\MediaPortal\xbmc\bin\Debug\MediaPortal.vshost.exe'.
Additional Information: DLL 'D:\Projects\MediaPortal\xbmc\bin\Debug\Microsoft.DirectX.Direct3D.dll' is 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.​

The following module was built either with optimizations enabled or without debug information:
xbmc\bin\debug\core.dll​

Managed Debugging Assistant 'LoaderLock' has detected a problem in 'D:\Projects\MediaPortal\xbmc\bin\Debug\MediaPortal.vshost.exe'.
Additional Information: DLL 'D:\Projects\MediaPortal\xbmc\bin\Debug\Microsoft.DirectX.dll' is 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.​

 

[CHli]

Managed Debugging Assistant 'LoaderLock' has detected a problem in 'D:\Projects\MediaPortal\xbmc\bin\Debug\MediaPorta l.vshost.exe'.
Additional Information: DLL 'D:\Projects\MediaPortal\xbmc\bin\Debug\Microsoft. DirectX.Direct3D.dll' is 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 is a well known problem when using an old version of Managed DirectX, you can hide it by going in Menu Debug/Exceptions... then select Managed Debugging Assistant and unticking LoaderLock.

About this :

The following module was built either with optimizations enabled or without debug information:
xbmc\bin\debug\core.dll

You should have a look how the Core project is build and add Debug informations in project properties.

Enjoy.

 

[gloomyandy]

This is a well known problem when using an old version of using Managed DirectX, you can hide it by going in Menu Debug/Exceptions... then select Managed Debugging Assistant and unticking LoaderLock.

Hi I've also been seeing this exception. Can you give me any more background on what is causing it? Is there something on my system that I need to update, or is just something that the mp code is doing that I can safely ignore?

Thanks

Andy

 

[cwbynum]

This is a well known problem when using an old version of using Managed DirectX, you can hide it by going in Menu Debug/Exceptions... then select Managed Debugging Assistant and unticking LoaderLock.

What Menu? I don't see it in Tools->Options->Debugging.

Thanks for the Help.

 

[gloomyandy]

The Exceptions item is in the top level Debug menu, (which I think is only there when you have a project loaded).

Andy

 

[CHli]

More Infos there : http://www.thezbuffer.com/articles/304.aspx

 

[gloomyandy]

More Infos there : http://www.thezbuffer.com/articles/304.aspx

Perfect Thanks!

Andy