Re: [Bluez-users] nonblocking socket

Marcel Holtmann
2006-08-03T10:29:45Z

Hi Jeff,

> I am using bluez-libs-2.25 on 2.6.11-mh2 to develop BlueZ support for
> a multithreaded process. My BlueZ contribution opens a non-blocking
> RFCOMM socket in one thread, and blocking SDP query in another. So
> far, I have RFCOMM support working, and I have also integrated
> Bluetooth inquiry and SDP queries.
>
> When I set RFCOMM to nonblocking, the sdp_connect returns an error,
> with errno set to EALREADY. Why does one thread affect the other?
>
> This same SDP query worked fine before I change the RFCOMM to nonblocking.

can you provide a simple test program for this? It sounds like a strange
bug with threading. However why do you need a non-blocking socket when
you are using threading?

Regards

Marcel