Hi, On Wed, Jul 21, 2010 at 1:19 PM, Johan Hedberg <johan.hedberg@xxxxxxxxx> wrote: > I don't really understand the need for these changes, but admitedly the > function does have issues since it first checks for !ctxt->session and > then later for ctxt->session even though at that point it's already > guaranteed that ctxt->session is not NULL. Yep, I suspect it is something else too, there doesn't seems to be a call to bt_cancel_discovery in the last trace sent to the list, but the check for ctxt->session there seems buggy, we should always remove the context doesn't matter if it is connected or not. @Manuel: Does valgrind give you a nice bracktrace when it bluetoothd segfaults? Normally I use something like this: > sudo valgrind --trace-children=yes ./bluetoothd -dn -- 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
