Hi Danny, > >> A small patch to avoid ConnMan crash, NULL pointer reference. > >> When dbus removes timer and calls dbus_timeout_set_data, > >> timeout_handler_free didn't check whether its handler is NULL or not. > >> Following backtrace of ConnMan crash is included: > >> > >> > >> #0 timeout_handler_free (data=0x0) at gdbus/mainloop.c:203 > >> #1 0x42272654 in dbus_timeout_set_data (timeout=0x76f28, data=0x0, > >> free_data_function=0) at dbus-timeout.c:451 > >> #2 0x422726cc in _dbus_timeout_list_remove_timeout > >> (timeout_list=0x6cab0, > >> timeout=0x76f28) at dbus-timeout.c:347 > > >this backtrace should be also part of the commit message. > > > >And how do you manage to trigger this one actually. It should not happen in > >the first place. What D-Bus version are you using? > > > With DBUS 1.4.8, ConnMan has been tested over between Wi-Fi, Wi-Fi direct > (with Broadcom dhd) and Mobile AP (also Broadcom solution). > ConnMan only works with pure Wi-Fi environment and direct and mobile ap with > Broadcom proprietary solution.
are you running a plain upstream D-Bus 1.4.8 or do you have modifications on top of it. I try to figure out on how get this _dbus_timeout_list_remove_timeout call in this case. I don't think it should happen. Do you have a guideline for me on how to reproduce this bug and get this backtrace by myself. Regards Marcel _______________________________________________ connman mailing list [email protected] http://lists.connman.net/listinfo/connman
