Re: Is there a problem with Bluetooth operations and multi-threading?
Re: Is there a problem with Bluetooth operations and multi-threading?
- Subject: Re: Is there a problem with Bluetooth operations and multi-threading?
- From: Marco Pontil <email@hidden>
- Date: Wed, 28 Jan 2004 14:48:50 -0800
There is no known no problem with the application quitting while doing
bluetooth transactions. However the bluetooth stack is not thread safe.
So you must run all the bluetooth code in the same thread.
... Marco
On Jan 28, 2004, at 1:40 PM, Crichlow, Eric wrote:
When I exit my application while a second thread exists which is
trying
to connect to a Bluetooth device, I can't launch the application
again. I
get the error message:
"The operation could not be completed. An unexpected error occurred
(error
code -600)."
After doing some testing, it appears as though the OS still thinks
the
app is running. I found this out by trying to trash the application,
but the
Finder won't let me because it says the app is open. Well, I check
Activity
Monitor and see that the app isn't running anymore, but you can't
convince
the Finder of that.
I have narrowed the situation down somewhat. This problem only
happens
in 10.3 (10.3.2). Everything works fine in 10.2.x.
Is there something bad that happens if the app exits while one of
its
threads was in the middle of a openRFCOMMChannel or other such
Bluetooth
call?
...Thanx...
...Eric...
_______________________________________________
bluetooth-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/bluetooth-dev
Do not post admin requests to the list. They will be ignored.
_______________________________________________
bluetooth-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/bluetooth-dev
Do not post admin requests to the list. They will be ignored.