Author Topic: First-chance exception problem  (Read 2761 times)

Offline tree1891

  • Newbie
  • *
  • Posts: 14
  • Karma: 0
First-chance exception problem
« on: December 09, 2011, 05:32:29 AM »
I have executed BluetoothDiscoveryDemo.exe, but debugger continue logging such below.

....
First-chance exception at 0x7546d36f in BluetoothDiscoveryDemo.exe: 0x8001010E: The application called an interface that was marshalled for a different thread.
....

Other samples behave same.

What's problem?


Online Mike Petrichenko

  • Bluetooth Framework Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 3052
  • Karma: 1000
    • Soft Service Company
Re: First-chance exception problem
« Reply #1 on: December 09, 2011, 08:07:36 AM »
What is you OS, WCL version and Bluetooth driver?

Offline tree1891

  • Newbie
  • *
  • Posts: 14
  • Karma: 0
Re: First-chance exception problem
« Reply #2 on: December 09, 2011, 09:03:08 AM »
OS: windows7 sp1
Bluetooth driver: BlueSoleil v8.0.356
WCL 6.9.3.0

Thank a lot

Online Mike Petrichenko

  • Bluetooth Framework Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 3052
  • Karma: 1000
    • Soft Service Company
Re: First-chance exception problem
« Reply #3 on: December 09, 2011, 09:21:50 AM »
Looks like something wrong with your IDE or drivers. Have just tested it on Win 7 with BS 8.0.356 using VS 2005, VS 2008, VS 2010 and VS 11 - all works.

Offline tree1891

  • Newbie
  • *
  • Posts: 14
  • Karma: 0
Re: First-chance exception problem
« Reply #4 on: December 09, 2011, 09:28:40 AM »
Of course, it works well, but continue logging first-chance exception message.
Have you checked it's debug log in vs2010?

I checked it in vs 2010 debug mode with Exception messages checked

Thank a lot

Online Mike Petrichenko

  • Bluetooth Framework Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 3052
  • Karma: 1000
    • Soft Service Company
Re: First-chance exception problem
« Reply #5 on: December 09, 2011, 09:38:50 AM »
I reproduced the message. But this is not WCL message. The address is somewhere in driver what is absolutely out of my control. Exception code says that its RPC error. WCL doesn't use RPC.

 

Sitemap 1 2 3 4 5 6 7 8 9