"Managed Debugging Assistant 'LoaderLock' has detected a problem in - microsoft.public.dotnet.framework.clr

Message from discussion "Managed Debugging Assistant 'LoaderLock' has detected a problem in

mohan@tek.com

View profile

More options 6 Jun 2006, 08:25

Newsgroups: microsoft.public.dotnet.framework.clr

From: "mo...@tek.com" <mo...@tek.com>

Date: 6 Jun 2006 00:25:35 -0700

Local: Tues 6 Jun 2006 08:25

Subject: Re: "Managed Debugging Assistant 'LoaderLock' has detected a problem in

  Reply to author
  |
  Forward | Print | View thread
  | Show original
  | Report this message | Find messages by this author
  

Hi Greg,

Thanks very much.

Problem1:
I am using some managed dll which will be calling the unmaged
dll(tekSpy.dll).
The unmanaged dll is calling win32 dll for doing code injection. i.e
it will be accesing managed exe through hook process.

Once I unchecked the Loder lock exception thrown option from
Debug->Exceptions,I am not getting the messgae. But I am not sure that
, this will be the permanent solution.

Pls let me know your thoughts.

Problem 2:
I got your point. But I dont know how to call main form instance
through control.invoke.
Especially how to assign mainform instance to delegate?

Thanks,
Mohan

Greg Young wrote:
> Problem 1: Are you using any other dlls? Basically it is saying that the
> TekSpyHook DLL is accessing another DLL in its DLLMain which is a big no no.
> Is this your own DLL or from somewhere else?

> Problem 2: You can only access controls on the thread that they were created
> on. You should be using Invoke/BeginInvoke in order to marshal operations on
> controls back to the main thread. If you do a google on VB.NET control
> invoke (or begininvoke) you can find a ton of articles .. here is one from
> msdn mag
> http://msdn.microsoft.com/msdnmag/issues/04/05/BasicInstincts/default....
> Basically in 2.0 its alerting you that you have a threading problem where as
> it did not in 1.x.

> Cheers,

> Greg Young
> MVP - C#
> http://geekswithblogs.net/gyoung

> <mo...@tek.com> wrote in message
> news:1149489172.672028.192690@i39g2000cwa.googlegroups.com...
> > Hi all,

> > I have ported my VB.Net project from VS2003 to VS2005. I am facing two
> > issues while running my applications:
> > Issue1:
> > I am calling some managed dlls (developed in C#) from my Vb .net .
> > Whne I
> > debug the code,Iam getting the following Error message.

> > "Managed Debugging Assistant 'LoaderLock' has detected a problem in
> > 'F:\VBSource\bin\Debug\TekRobo.exe'.
> > Additional Information: DLL 'F:\VBSource\bin\Debug\Tekspyhook.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."

> > How to resolve the above error?

> > i ssue2:

> > I am calling mainform instance (static variable) from other VB .net
> > modules
> > from the same projects.In VS2003 ,I did not face any issues. But in
> > VS2005 ,I
> > am getting the following exception. P.s I am running the application
> > under
> > thread.

> > "A first chance exception of type 'System.InvalidOperationException'
> > occurred in System.Windows.Forms.dll
> > Additional information: Cross-thread operation not valid: Control
> > 'StressTest' accessed from a thread other than the thread it was
> > created on."

> > it would be greatful ,if any one help me to resolve the above two
> > issues.
> > Thanks
> > Mohan
> > Was this

Reply to author Forward