Problems with dbus_fake_mutex
alexl at redhat.com
Thu Nov 23 01:25:25 PST 2006
On Thu, 2006-11-23 at 09:49 +0100, Christian Ehrlicher wrote:
> During our work on the win32 port, we found a problem with
> dbus_fake_mutex_foo() - functions. Because they're only fake
> functions, it is possible that one thread looks something and another
> thread wants to access the locked variable. Instead waiting for
> unlock, the thread throws an assert().
> Now I wonder why you added those fake mutexes. You should get the same
> problems on linux too (not that often because we use more locks)...
You can't use the fake mutexes with actual threads. If you use threads
you *have* to initialize dbus with thread support.
The fake mutexes are there to use in tests to detect bugs like
Alexander Larsson Red Hat, Inc
alexl at redhat.com alla at lysator.liu.se
He's a maverick bohemian filmmaker with acid for blood. She's a psychotic
antique-collecting college professor from a family of eight older brothers.
They fight crime!
More information about the dbus