On Tue, Jan 26, 2010 at 9:09 AM, Luiz Augusto von Dentz <luiz.dentz@xxxxxxxxx> wrote: > Hi Claudio, > > On Mon, Jan 25, 2010 at 8:14 PM, Claudio Takahasi > <claudio.takahasi@xxxxxxxxxxxxx> wrote: >> Hi Johan/Luiz, >> >> I found an error "invalid read". The pastebin log shows a PBAP >> connection in the RFCOMM channel 15. See line 195 of the first log, >> when the connection is refused the "temporary" device is being >> removed, however it seems that the "reverse" SDP query still active. >> PTS is establishing RFCOMM connection before "Encrypt Change" event, >> but this wrong procedure should not "harm" bluetoothd. In some cases I >> noticed segmentation fault, probably due this error. >> >> http://pastebin.com/m308f85ef >> http://pastebin.com/m2d80dd71 > > Does this fix the problem: > > diff --git a/src/device.c b/src/device.c > index a2730ab..dfdacd8 100644 > --- a/src/device.c > +++ b/src/device.c > @@ -239,6 +239,9 @@ static void device_free(gpointer user_data) > if (device->disconn_timer) > g_source_remove(device->disconn_timer); > > + if (device->discov_timer) > + g_source_remove(device->discov_timer); > + > debug("device_free(%p)", device); > > g_free(device->authr); > > > -- > Luiz Augusto von Dentz > Engenheiro de Computação > Hi Luiz, yep, it is working perfectly: no warning/no segmentation fault. Claudio. -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
