Date: Tue, 23 Jul 2013 16:43:28 +0100 From: Martin Simmons <martin@lispworks.com> To: Joe Marcus Clarke <marcus@marcuscom.com> Cc: deischen@freebsd.org, kwm@rainbow-runner.nl, avg@freebsd.org, freebsd-threads@freebsd.org Subject: Re: Mutexes and error checking Message-ID: <201307231543.r6NFhS7n007384@higson.cam.lispworks.com> In-Reply-To: <51EC49F8.6070207@marcuscom.com> (message from Joe Marcus Clarke on Sun, 21 Jul 2013 16:52:08 -0400) References: <51E71D4F.5030502@marcuscom.com> <Pine.GSO.4.64.1307181059460.22570@sea.ntplx.net> <51E8061B.60906@marcuscom.com> <Pine.GSO.4.64.1307181118100.22570@sea.ntplx.net> <Pine.GSO.4.64.1307182144030.23634@sea.ntplx.net> <Pine.GSO.4.64.1307190152440.25756@sea.ntplx.net> <51EB5EC4.6050802@marcuscom.com> <20130721160220.GA38417@stack.nl> <51EC0BCF.6080501@FreeBSD.org> <51EC49F8.6070207@marcuscom.com>
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 (https://bugzilla.gnome.org/show_bug.cgi?id=678758) should be fixed, not ignored by hiding the error status. __Martin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201307231543.r6NFhS7n007384>