Did you know ...
Search Documentation:
Predicate mutex_unlock_all/0
HOME
DOWNLOAD
SWI-Prolog
Sources/building
Docker images
Add-ons
Browse GIT
DOCUMENTATION
Manual
Packages
FAQ
Command line
PlDoc
Bluffers
▶
Prolog syntax
PceEmacs
HTML generation
License
Publications
Rev 7 Extensions
TUTORIALS
Beginner
▶
Getting started
Learn Prolog Now!
Simply Logical
Debugger
Development tools
Advanced
▶
Modules
Grammars (DCGs)
clp(fd)
Printing messages
PlDoc
Web applications
▶
Web applications
Let's Encrypt!
Pengines
Semantic web
▶
ClioPatria
RDF namespaces
Graphics
▶
XPCE
GUI options
Machine learning
▶
Probabilistic Logic Programming
External collections
▶
Meta level tutorials
For packagers
▶
Linux packages
COMMUNITY
IRC
Forum & mailing list
Blog
News
Report a bug
Submit a patch
Submit an add-on
Roadmap (on GitHub)
External links
Contributing
Code of Conduct
Contributors
SWI-Prolog items
USERS
Semantic web
Students
Researchers
Commercial users
Dog food
Is SWIPL right for me?
WIKI
Login
View changes
Sandbox
Wiki help
All tags
Documentation
Reference manual
Multithreaded applications
Thread synchronisation
mutex_create/1
mutex_create/2
mutex_destroy/1
with_mutex/2
mutex_lock/1
mutex_trylock/1
mutex_unlock/1
mutex_unlock_all/0
mutex_property/2
Packages
Availability:
built-in
[deprecated]
mutex_unlock_all
Unlock all mutexes held by the current thread. This predicate should not be needed if mutex unlocking is guaranteed with
with_mutex/2
or
setup_call_cleanup/3
.
205
The also deprecated
thread_exit/1
bypasses the automatic cleanup.