From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Bossom, John" <John.Bossom@Cognos.COM>
To: 'Scott McCaskill' <scott@magruder.org>, pthreads-win32@sources.redhat.com
Subject: RE: destroying a locked mutex
Date: Tue, 24 Jul 2001 10:04:00 -0000
Message-id: <430F887D415DD1118C2700805F31ECF104AFA5B4@sota0005.cognos.com>
X-SW-Source: 2001/msg00067.html

The book, Programming with POSIX Threads indicates that
pthread_mutex_destroy has the
following return values:

Errors:
	[EBUSY]	mutex is in use.
	[EINVAL]	mutex is invalid.

Hint: Safets after unlocking mutex, when no other threads will lock.


Multithreaded Programmin with PThreads:
	[EBUSY]	Attempt to destroy a locked mutex.

-----Original Message-----
From: Scott McCaskill [ mailto:scott@magruder.org ]
Sent: July 24, 2001 12:15 PM
To: pthreads-win32@sources.redhat.com
Subject: destroying a locked mutex


Should pthread_mutex_destroy() return an error if the mutex is locked?
pthreads-win32 seems to disagree with the linux implementation of pthreads
on this point (OK on windows, not on linux).