Memory-managed wrapper type.

Construct a Cond struct initialized to zero.

If threads are waiting for cond, all of them are unblocked. If no threads are waiting for cond, this function has no effect. It is good practice to lock the same mutex as the waiting threads while calling this function, though not required.

Frees the resources allocated to a Cond with condInit.

This function should not be used with a Cond that has been statically allocated.

Calling condClear for a Cond on which threads are blocking leads to undefined behaviour.

Since: 2.32

Initialises a Cond so that it can be used.

This function is useful to initialise a Cond that has been allocated as part of a larger structure. It is not necessary to initialise a Cond that has been statically allocated.

To undo the effect of condInit when a Cond is no longer needed, use condClear.

Calling condInit on an already-initialised Cond leads to undefined behaviour.

Since: 2.32

If threads are waiting for cond, at least one of them is unblocked. If no threads are waiting for cond, this function has no effect. It is good practice to hold the same lock as the waiting thread while calling this function, though not required.

Atomically releases mutex and waits until cond is signalled. When this function returns, mutex is locked again and owned by the calling thread.

When using condition variables, it is possible that a spurious wakeup may occur (ie: condWait returns even though condSignal was not called). It's also possible that a stolen wakeup may occur. This is when condSignal is called, but another thread acquires mutex before this thread and modifies the state of the program in such a way that when condWait is able to return, the expected condition is no longer met.

For this reason, condWait must always be used in a loop. See the documentation for Cond for a complete example.

Waits until either cond is signalled or endTime has passed.

As with condWait it is possible that a spurious or stolen wakeup could occur. For that reason, waiting on a condition variable should always be in a loop, based on an explicitly-checked predicate.

True is returned if the condition variable was signalled (or in the case of a spurious wakeup). False is returned if endTime has passed.

The following code shows how to correctly perform a timed wait on a condition variable (extending the example presented in the documentation for Cond):

C code

gpointer
pop_data_timed (void)
{
  gint64 end_time;
  gpointer data;

  g_mutex_lock (&data_mutex);

  end_time = g_get_monotonic_time () + 5 * G_TIME_SPAN_SECOND;
  while (!current_data)
    if (!g_cond_wait_until (&data_cond, &data_mutex, end_time))
      {
        // timeout has passed.
        g_mutex_unlock (&data_mutex);
        return NULL;
      }

  // there is data for us
  data = current_data;
  current_data = NULL;

  g_mutex_unlock (&data_mutex);

  return data;
}

Notice that the end time is calculated once, before entering the loop and reused. This is the motivation behind the use of absolute time on this API -- if a relative time of 5 seconds were passed directly to the call and a spurious wakeup occurred, the program would have to start over waiting again (which would lead to a total wait time of more than 5 seconds).

Since: 2.32