/usr/local/lib/swipl/library/threadutil.pl
All Application Manual Name SummaryHelp

  • swipl
    • library
      • error.pl
      • debug.pl
      • apply.pl
      • lists.pl
      • broadcast.pl
      • shlib.pl
      • option.pl
      • thread_pool.pl
      • gensym.pl
      • settings.pl -- Setting management
      • arithmetic.pl
      • main.pl
      • readutil.pl
      • operators.pl
      • pairs.pl -- Operations on key-value lists
      • prolog_source.pl
      • record.pl -- Access compound arguments by name
      • predicate_options.pl
      • sandbox.pl
      • apply_macros.pl -- Goal expansion rules to avoid meta-calling
      • yall.pl
      • assoc.pl
      • prolog_format.pl -- Analyse format specifications
      • quasi_quotations.pl
      • pure_input.pl -- Pure Input from files and streams
      • solution_sequences.pl
      • ordsets.pl
      • random.pl
      • base64.pl
      • aggregate.pl
      • csv.pl -- Process CSV (Comma-Separated Values) data
      • pprint.pl
      • atom.pl
      • modules.pl
      • occurs.pl
      • prolog_xref.pl
      • prolog_colour.pl
      • lazy_lists.pl
      • ugraphs.pl
      • url.pl
      • www_browser.pl
      • prolog_pack.pl
      • git.pl
      • utf8.pl
      • dialect.pl
      • system.pl -- System utilities
      • terms.pl
      • date.pl
      • persistency.pl
      • iostream.pl -- Utilities to deal with streams
      • prolog_stack.pl -- Examine the Prolog stack
      • edinburgh.pl -- Some traditional Edinburgh predicates
      • prolog_clause.pl
      • prolog_breakpoints.pl
      • wfs.pl
      • prolog_code.pl
      • sort.pl
      • dicts.pl
      • dif.pl
      • varnumbers.pl
      • pio.pl
      • base32.pl
      • charsio.pl -- I/O on Lists of Character Codes
      • codesio.pl
      • coinduction.pl
      • heaps.pl
      • rbtrees.pl
      • statistics.pl
      • when.pl
      • backcomp.pl
      • prolog_wrap.pl -- Wrapping predicates
      • threadutil.pl -- Interactive thread utilities
        • threads/0
        • join_threads/0
        • with_stopped_threads/2
        • thread_has_console/0
        • attach_console/0
        • attach_console/1
        • tspy/1
        • tspy/2
        • tdebug/0
        • tdebug/1
        • tnodebug/0
        • tnodebug/1
        • tbacktrace/1
        • tbacktrace/2
        • tprofile/1
        • thread_alias/1
      • writef.pl
      • prolog_trace.pl
      • ansi_term.pl
      • prolog_debug.pl -- User level debugging tools
      • optparse.pl
      • tty.pl
      • edit.pl
      • macros.pl
      • listing.pl -- List programs and pretty print clauses
      • intercept.pl
      • nb_set.pl -- Non-backtrackable sets
      • prolog_codewalk.pl
      • prolog_metainference.pl
      • ctypes.pl -- Character code classification
      • make.pl
      • check.pl -- Consistency checking
      • hashtable.pl
      • increval.pl
      • tables.pl -- XSB interface to tables
      • fastrw.pl
      • portray_text.pl
      • thread.pl
      • prolog_coverage.pl
      • streams.pl -- Manage Prolog streams
      • oset.pl
      • shell.pl -- Elementary shell commands
      • strings.pl
      • files.pl
      • prolog_autoload.pl
      • prolog_versions.pl
      • rwlocks.pl
      • prolog_qlfmake.pl -- Compile the library to QLF format
      • exceptions.pl
 tdebug is det
 tdebug(+ThreadOrClass) is det
 tnodebug is det
 tnodebug(+ThreadOrClass) is det
Enable or disable a thread or group of threads for debugging using the graphical tracer. A group of threads is addressed based on the class property of a thread set by thread_create/3 or set_thread/2. This implies loading the graphical tracer and switching the thread to debug mode using debug/0. New threads created inherit their debug mode from the thread that created them.

Thread classes have been introduced in SWI-Prolog 10.0.2/10.1.5. This allows for more selective debugging as well as ensuring debugging works in newly created threads. For example, the HTTP server creates all its worker threads in the class http. Using query below, we reliable make sure spy points are trapped in HTTP handler threads, regardless of whether the worker existed or is lazily created and regardless of whether the user switched to nodebug mode while tracing a previous event (see debug_reset_from_class/0).

?- tdebug(http).