[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [bluetooth-dev] dirty code in bt_disconnect
> -----Original Message-----
> From: Ilguiz Latypov [mailto:firstname.lastname@example.org]
> Sent: 05 October 2001 15:41
> To: Matthias Fuchs
> Cc: OpenBT Development List
> Subject: Re: [bluetooth-dev] dirty code in bt_disconnect
> a) I agree that the code retrieved off CVS repository at
> sourceforge.net doesn't have initialization for the line variable
> in bt_disconnect() when PSM is one of L2CAP_TEST*_LAYER.
> b) Can anybody explain what is the purpose of monitoring file
> descriptor 0 in the main() function in apps/bluetooth/experimental/btd.c.
> The FD_SET() macro adds file descriptor 0 to the set of monitored desciptors.
I have no idea why it is including stdin in the read set...
> c) The other issue: the handling of events from the
> descriptor 0 is empty when the "IP assign" feature is disabled.
Well, it does just as much for stdin when the IP assigner is enabled,
> Besides, the "IP assign" Unix socket contains a for-loop
> where the body doesn't depend on the loop count. We are
> not using the "IP assign" feature.
Where is this code?
> On Fri, 5 Oct 2001, Matthias Fuchs wrote:
> > while compiling the openbt lkm gcc told me about an uninitialized
> > variable in function bt_disconnect in bluetooth.c.
To unsubscribe from this list: send the line "unsubscribe bluetooth-dev" in
the body of a message to email@example.com