Forms.UnsafeNativeMethods+IMsoComponentManager.FPushMessageLoop

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • roni

    #1

    Forms.UnsafeNativeMethods+IMsoComponentManager.FPushMessageLoop

    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.Applicati on.ComponentMan ager.System.Win dows.Forms.Unsa f
    eNativeMethods+ IMsoComponentMa nager.FPushMess ageLoop


    can anyone explain what's that mean ?


  • roni

    #2
    more info

    hi again.
    just to add more info ,
    this
    System.Windows. Forms.Applicati on.ComponentMan ager.System.Win dows.Forms.Unsa f[color=blue]
    > eNativeMethods+ IMsoComponentMa nager.FPushMess ageLoop[/color]


    is happen after i call Application:DoE vents from the managed c++ .


    "roni" <ronixnow@hotma il.com> wrote in message
    news:d3g60c$9eq $1@news2.netvis ion.net.il...[color=blue]
    > 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[/color]
    wrong[color=blue]
    > 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
    >[/color]
    System.Windows. Forms.Applicati on.ComponentMan ager.System.Win dows.Forms.Unsa f[color=blue]
    > eNativeMethods+ IMsoComponentMa nager.FPushMess ageLoop
    >
    >
    > can anyone explain what's that mean ?
    >
    >[/color]


    Comment

    Working...