David Zeuthen 11e01802ab gdbus-codegen: Ensure that generated skeletons are MT-safe ... For example, if setting a property on a skeleton from another thread than where it was constructed, the idle handler responsible for emitting the PropertiesChanged() signal could run immediately and clear skeleton->priv->changed_properties_idle_source causing g_source_unref() to be called with a NULL pointer. This race was easily be fixed by adding a lock to the skeleton object. In addition to fixing this race, also move the code for setting up the idle handler to a class handler for the GObject::notify signal. This change allows use of g_object_freeze_notify() and g_object_thaw_notify() to perform atomic property changes from another thread than the one that the skeleton was created in. Signed-off-by: David Zeuthen <davidz@redhat.com>		2011-05-15 12:38:24 -04:00
..
reference	gdbus-codegen: Ensure that generated skeletons are MT-safe	2011-05-15 12:38:24 -04:00
debugging.txt	Remove references to gruntime. This includes renaming the test program	2002-02-26 21:23:52 +00:00
macros.txt	honour g_mem_gc_friendly settings when freeing slices, make sure	2006-01-25 15:51:43 +00:00
Makefile.am	initialize automake variables EXTRA_DIST and TEST_PROGS for unconditional	2007-11-21 20:09:46 +00:00