[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [bluetooth-dev] SDP problem...
Ok, I found the problem.
Someone has modified the structure data_struct in sdp.c and sdp_server.c
changing the s32 member variables to u16 and not giving the packed attribute
to this structure.
I would like to tell to this one person, that I am sick of having the same
bugs again, and again. I am sick not to be heard when I say not to cast a
struct to an (u8*). This person, instead of modify this dirty code, should
have rewritten properly the code which in the case of SDP is not such a big
deal. I will not do it as I have lost enough of my time.
In fact it makes sense not to include this stack in the standard kernel tree
as porting issues are prohibitive...
This kind of recurent problem could make people work on the bluez stack
instead of the openbt (although the rfcomm of bluez also uses these silly
structures (probably copied from openbt)).
Le Jeudi 21 Juin 2001 16:15, vous avez écrit :
> Can someone explain me the way sdp_database_write works in sdp.c ?
> Where is db_write_recv initialised ?
> The debug output says :
> sdp_database_write Someone wrote 8 bytes to sdp proc-file
> sdp_database_write Someone wrote 7 bytes to sdp proc-file
> SDP sdp_database_write preparing to send 7 bytes data to
> Which part of the data received from the server is actually sent inside a
> L2CAP packet ?
> To unsubscribe from this list: send the line "unsubscribe bluetooth-dev" in
> the body of a message to firstname.lastname@example.org
To unsubscribe from this list: send the line "unsubscribe bluetooth-dev" in
the body of a message to email@example.com