Re: Leopard and RFCOMM...
Re: Leopard and RFCOMM...
- Subject: Re: Leopard and RFCOMM...
- From: Joseph Kelly <email@hidden>
- Date: Mon, 12 Nov 2007 09:38:58 -0800
To follow up on this:
This was my own mistake: I found that I was passing a raw CFData byte
pointer (obtained from a message port callback) to the main thread
without first retaining it. The message port callback would return,
free the data, and in the main thread I would then RFCOMM-write the
now invalid data. Apparently Leopard has instituted some new policy
whereby the OS reclaims and re-uses freed memory ;-)
Joe K.
On Oct 29, 2007, at 3:57 PM, Joseph Kelly wrote:
Is there any known issues with RFCOMM running on Leopard?
I can write data to my company's device, but every once in a while,
I stop receiving expected data.
This was working on 10.4.10.
If not, I'll file a bug.
Joe K.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Bluetooth-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Bluetooth-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden