Re: Explaining cond var destroy [Re: [musl] C threads, v3.0]

[Jens Gustedt <jens.gustedt@inria.fr>]

[-- Attachment #1: Type: text/plain, Size: 985 bytes --]

Am Mittwoch, den 06.08.2014, 18:04 -0400 schrieb Rich Felker:
> No. The problem is that the memory in which the cond var resides could
> previously have been used for a mutex, semaphore, or other object for
> which a futex wait arrives "very late" due to scheduling. It has
> nothing to do with the destruction of cond vars.

Hm, but then we have a problem on the side that has this late wait,
that is an access to a dead object. So the UB is there, in that thread
that is doing the wait. (Suppose it is just threads and not processes,
that would even be more complicated.) That spurious wakeup that you
are talking about is a consequence of UB.

good night

Jens

-- 
:: INRIA Nancy Grand Est ::: AlGorille ::: ICube/ICPS :::
:: ::::::::::::::: office Strasbourg : +33 368854536   ::
:: :::::::::::::::::::::: gsm France : +33 651400183   ::
:: ::::::::::::::: gsm international : +49 15737185122 ::
:: http://icube-icps.unistra.fr/index.php/Jens_Gustedt ::



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]