Forms.UnsafeNativeMethods+IMsoComponentManager.FPu shMessageLoop

[roni]

hi.

i have vb.net application , with Managed C++ dll that wrap unmanaged dll.

i also have bug that crash the application.

the crash happen because i dont use the unmanaged dll (which is
dialogic -telephony dll)
in the right way.

i can reproduce the crash (not the main bug im looking, but i found mini
bug, that also cause the crash,and from that im going to learn what's wrong
here)

the application is multi thread.
when im starting to trace\debug the bug,i see in the "threads" windows
in the location of some thread somthing like this :
Thread ID 2333 LOCATION
System.Windows.Forms.Application.ComponentManager. System.Windows.Forms.Unsaf
eNativeMethods+IMsoComponentManager.FPushMessageLo op
can anyone explain what's that mean ?

[roni]

hi again.
just to add more info ,
this
System.Windows.Forms.Application.ComponentManager. System.Windows.Forms.Unsaf

eNativeMethods+IMsoComponentManager.FPushMessageLo op

is happen after i call Application:DoEvents from the managed c++ .
"roni" <ro******@hotmail.com> wrote in message
news:d3**********@news2.netvision.net.il... hi.

i have vb.net application , with Managed C++ dll that wrap unmanaged dll.

i also have bug that crash the application.

the crash happen because i dont use the unmanaged dll (which is
dialogic -telephony dll)
in the right way.

i can reproduce the crash (not the main bug im looking, but i found mini
bug, that also cause the crash,and from that im going to learn what's wrong here)

the application is multi thread.
when im starting to trace\debug the bug,i see in the "threads" windows
in the location of some thread somthing like this :
Thread ID 2333 LOCATION
System.Windows.Forms.Application.ComponentManager. System.Windows.Forms.Unsaf eNativeMethods+IMsoComponentManager.FPushMessageLo op
can anyone explain what's that mean ?