> All the stuff in the protect-callbacks branch looks good, please push.
> I couldn't trigger crashes on a number of devices just pulling them out
> in the middle of a tight loop hammering the modem for info. Good work.
>
This has been pushed to both git master and MM_05.
Cheers,
--
Aleksand
On Tue, 2011-05-17 at 09:57 +0200, Aleksander Morgado wrote:
> Hi Dan,
>
> > > >
> > > > Each MMCallbackInfo holds a weak reference to the MMModem to which the
> > > > AT command was sent. When the MMModem is destroyed,
> > > > mm-callback-info.c::modem_destroyed_cb() gets called and the modem
>
Hi Dan,
> > >
> > > Each MMCallbackInfo holds a weak reference to the MMModem to which the
> > > AT command was sent. When the MMModem is destroyed,
> > > mm-callback-info.c::modem_destroyed_cb() gets called and the modem
> > > pointer in the callback info is reset to NULL, to avoid having a poin
> >
> > Each MMCallbackInfo holds a weak reference to the MMModem to which the
> > AT command was sent. When the MMModem is destroyed,
> > mm-callback-info.c::modem_destroyed_cb() gets called and the modem
> > pointer in the callback info is reset to NULL, to avoid having a pointer
> > to an alre
On Wed, 2011-05-11 at 16:20 +0200, Aleksander Morgado wrote:
> Hi all,
>
> Each MMCallbackInfo holds a weak reference to the MMModem to which the
> AT command was sent. When the MMModem is destroyed,
> mm-callback-info.c::modem_destroyed_cb() gets called and the modem
> pointer in the callback inf
