StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POWhen can a cond var be used to synchronize its own destruction/unmapping?
text
Body
copied!<p>According to POSIX,</p> <blockquote> <p>It shall be safe to destroy an initialized condition variable upon which no threads are currently blocked.</p> </blockquote> <p>Further, the signal and broadcast operations are specified to unblock one/all threads blocked on the condition variable.</p> <p>Thus, it seems to me the following forms of self-synchronized destruction should be valid, i.e. calling <code>pthread_cond_destroy</code>:</p> <ol> <li>Immediately after a successful signal, in either the waiting or the signaling thread, when exactly one thread is blocked on the cond var.</li> <li>Immediately after a successful broadcast, in either any waiting thread or the broadcasting thread.</li> </ol> <p>Of course this assumes no further waiters will arrive and no further signals shall be performed afterwards, which the application is responsible for guaranteeing if using <code>pthread_cond_destroy</code>.</p> <p>Am I correct that destruction is valid in these situations? And are there other self-synchronized destruction scenarios to be aware of with condition variables?</p> <p>Finally, for process-shared cond vars where unmapping the shared mapping without destruction might make sense, is it reasonable to expect unmapping to be valid in the same contexts destruction would be valid, or must further synchronization be performed if multiple threads in the same process (address space) are using the same mapping and want to unmap it in one of the above contexts?</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload