Cleaning up after timer_delete

Rémi Denis-Courmont remi@remlab.net
Sun Jul 26 08:42:00 GMT 2009


Le dimanche 26 juillet 2009 11:30:49 Rémi Denis-Courmont, vous avez écrit :
> > I think the solution is going to be the other way around, the callback
> > has to know you are about to delete the timer and avoid touching the
> > resource.
>
> The only piece of data that the lock has is the pointer.

I meant the timer - the timer has a single pointer from which the location of 
the lock and the protected resources must be inferred.

-- 
Rémi Denis-Courmont
http://www.remlab.net/



More information about the Libc-help mailing list