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 [thread overview]
Message-ID: <430F887D415DD1118C2700805F31ECF104AFA5B4@sota0005.cognos.com> (raw)
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).
next reply other threads:[~2001-07-24 10:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-24 10:04 Bossom, John [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-25 3:32 Alexander Terekhov
2001-07-24 11:12 Bossom, John
2001-07-24 10:50 Alexander Terekhov
2001-07-24 9:46 Alexander Terekhov
2001-07-24 9:11 Scott McCaskill
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=430F887D415DD1118C2700805F31ECF104AFA5B4@sota0005.cognos.com \
--to=john.bossom@cognos.com \
--cc=pthreads-win32@sources.redhat.com \
--cc=scott@magruder.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).