Did you know ...
Search Documentation:
Simmulating a debugger interrupt
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
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
COMMERCIAL
WIKI
Login
View changes
Sandbox
Wiki help
All tags
Documentation
Reference manual
Hackers corner
Examining the Environment Stack
Ancestral cuts
Intercepting the Tracer
Simmulating a debugger interrupt
prolog_interrupt/0
Breakpoint and watchpoint handling
Adding context to errors: prolog_exception_hook
Hooks using the exception predicate
Prolog events
Hooks for integrating libraries
Hooks for loading files
Packages
B.4
Simmulating a debugger interrupt
prolog_interrupt
Calls the functionality that allows for debugging after receiving (normally)
SIGINT
. This may be used in IDE environments to start debugging a toplevel thread by injecting this into the target thread using
thread_signal/2
.