[http://www.sigfox.com/static/media/Y.png] <https://www.youtube.com/sigfox>
De : Aleksander Morgado
Envoyé : mercredi 28 novembre 2018 12:03:37
À : Sebastien Fabre
Cc : ModemManager (development)
Objet : Re: Crashes in g_hash_table_iter_next call
Hey,
>
Hey,
>
> > Have you not found the issue with MM 1.8? Or just not tried?
>
>
> We have not tried with MM 1.8 (we have not a method to reproduce these
> crashes).
>
> Do you think that "self->priv->ports" value should be checked before using it
> in all methods of mm-base-modem.c ? Or just destroy
ompany/2731408>
[http://www.sigfox.com/static/media/Y.png] <https://www.youtube.com/sigfox>
De : Aleksander Morgado
Envoyé : mardi 27 novembre 2018 17:43:59
À : Sebastien Fabre
Cc : ModemManager (development)
Objet : Re: Crashes in g_hash_table_i
Hey
> With different versions of ModemManager (1.6.12, 1.6.4, 1.4.2), we have seen
> (rarely) segfault crashes in g_hash_table_iter_next called by
> mm_base_modem_find_ports because the hash table corresponding to ports is
> NULL.
> When the crash occurs, in mm_base_modem_find_ports (mm-base-mo
Hello,
With different versions of ModemManager (1.6.12, 1.6.4, 1.4.2), we have seen
(rarely) segfault crashes in g_hash_table_iter_next called by
mm_base_modem_find_ports because the hash table corresponding to ports is NULL.
When the crash occurs, in mm_base_modem_find_ports (mm-base-modem.c),
