Subject: Re: Unlocking an unlocked mutex
To: Vincent <email@example.com>
From: Jason Thorpe <firstname.lastname@example.org>
Date: 10/13/2005 06:49:10
On Oct 13, 2005, at 1:28 AM, Vincent wrote:
> Jason Thorpe a =E9crit :
>> Yes, it's really an error. IMO, the thread library should abort =20
>> on such errors. It indicates that the app modified a data =20
>> structure it thought was locked, but in fact was not.
> Okay, I withdraw my proposal! ;)
> On the other hand, though I've not carried out a deep analysis, I =20
> wonder how a program that is known to work on Linux "as is" can =20
> generate this kind of error on NetBSD. Aren't both pthreads =20
> libraries (functionally) identical?
Linux's thread library simply doesn't report the error.
The app is incorrect, and should be fixed. NetBSD's thread library =20
is kind enough to tell you this fact.