Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 23 Jul 2013 16:43:28 +0100
From:      Martin Simmons <>
To:        Joe Marcus Clarke <>
Subject:   Re: Mutexes and error checking
Message-ID:  <>
In-Reply-To: <> (message from Joe Marcus Clarke on Sun, 21 Jul 2013 16:52:08 -0400)
References:  <> <> <> <> <> <> <> <> <> <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
>>>>> On Sun, 21 Jul 2013 16:52:08 -0400, Joe Marcus Clarke said:
> The specifics are this.  There are some GNOME/GTK+/GLib apps that are
> crashing now that GLib checks the return of pthread_mutex_unlock() in
> g_mutex_unlock().  While we can workaround this in GLib by simply
> nop'ing the EPERM return, we'd like to pursue something that may be a
> bit more manageable for those apps written for Linux that do not use GLib.

Which apps are broken and why can't they be fixed?

> Again, I'm not arguing the voracity of the 3rd party app code, just the
> discrepancy between Linux and Solaris compared to FreeBSD.

Note that unlocking an unlocked normal mutex on Linux (glibc) does *not* work,
but leaves it in a subtly inconsistent state.  Therefore bugs like the one you
reported to the GNOME Bugzilla
( should be fixed, not
ignored by hiding the error status.


Want to link to this message? Use this URL: <>