Hi, On Wed, Jul 21, 2010 at 6:11 PM, Manuel Naranjo <manuel@xxxxxxxxxxxx> wrote: > I think this is the one that really fix the problem. I see connect_watch > getting called and then getting into the crash. I have a nice log with the > tracing feature I sent the other day, here's the end of it (the hole thing > is almost 40 megs if someone wants just ask for it). I just figure out that our connect_watch in glib_helper.c is not quite right, it should be something similar as we have btio.c, specially this one is particular important: /* If the user aborted this connect attempt */ if ((cond & G_IO_NVAL) || check_nval(io)) return FALSE; It is probably because of not having this check that the cb is still called after bt_cancel_discovery. Of course this doesn't invalidate your fix to bt_cancel_discovery itself, but I guess this should also be included to safe that the callback is not called after cancelling the discovery. -- Luiz Augusto von Dentz Computer Engineer -- 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
