| /freebsd/secure/lib/libcrypto/man/man3/ |
| H A D | OSSL_trace_enabled.3 | 71 \&\- OpenSSL Tracing API
116 If the tracing facility is enabled (see "Configure Tracing" below),
117 these functions are used to generate free text tracing output.
119 The tracing output is divided into types which are enabled
121 The tracing types are described in detail in
126 Tracing for a specific category is enabled at run-time if a so-called
134 tracing code both channel types are effectively indistinguishable.
146 The tracing code normally does not call OSSL_trace_{begin,end}() directly,
150 \&\fBOSSL_trace_enabled()\fR can be used to check if tracing for the given
151 \&\fIcategory\fR is enabled, i.e., if the tracing facility has been statically
[all …]
|
| H A D | OSSL_trace_set_channel.3 | 81 If available (see "Configure Tracing" below), the application can request
89 to which the application can write the tracing output for this category.
94 For the tracing code, both trace channel types are indistinguishable.
98 \&\fBOSSL_TRACE_ENABLED\fR\|(3) can be used to check whether tracing is currently
111 tracing output.
115 tracing prefixes, consider setting a callback with
132 \&\fBOSSL_trace_set_callback()\fR with NULL for \fIcb\fR disables tracing for
175 exit from \f(CWmain()\fR, and any tracing output done during this cleanup
176 will be lost if the tracing channel or callback were cleaned away
346 .SS "Configure Tracing"
[all …]
|
| /freebsd/crypto/openssl/doc/man3/ |
| H A D | OSSL_trace_enabled.pod | 12 - OpenSSL Tracing API
59 If the tracing facility is enabled (see L</Configure Tracing> below),
60 these functions are used to generate free text tracing output.
62 The tracing output is divided into types which are enabled
64 The tracing types are described in detail in
69 Tracing for a specific category is enabled at run-time if a so-called
77 tracing code both channel types are effectively indistinguishable.
89 The tracing code normally does not call OSSL_trace_{begin,end}() directly,
95 OSSL_trace_enabled() can be used to check if tracing for the given
96 I<category> is enabled, i.e., if the tracing facility has been statically
[all …]
|
| H A D | OSSL_trace_set_channel.pod | 24 If available (see L</Configure Tracing> below), the application can request
32 to which the application can write the tracing output for this category.
37 For the tracing code, both trace channel types are indistinguishable.
41 L<OSSL_TRACE_ENABLED(3)> can be used to check whether tracing is currently
55 tracing output.
59 tracing prefixes, consider setting a callback with
76 OSSL_trace_set_callback() with NULL for I<cb> disables tracing for
132 exit from C<main()>, and any tracing output done during this cleanup
133 will be lost if the tracing channel or callback were cleaned away
316 =head2 Configure Tracing
[all …]
|
| /freebsd/share/man/man4/ |
| H A D | hwt.4 | 30 framework provides infrastructure for hardware-assisted tracing.
39 The framework supports several tracing technologies found on
73 This request allocates kernel tracing context (CTX) based on requested mode of
81 where ident is a unique identification number of tracing context, d is either
84 During tracing of a target process, HWT records runtime events such as threads
91 This pause allows user-space tools to retrieve the records and adjust tracing
94 allowing tracing of specific functions within the target executable or a
112 Start tracing.
113 In HWT CPU mode the tracing does actually start with this
116 In the Thread mode, the tracing "running" flag set, but tracing begins after
[all …]
|
| H A D | kcov.4 | 65 The thread then enables coverage tracing, with coverage data being written by
67 When tracing is disabled, the kernel relinquishes its access to the shared
74 The state of the tracing buffer can be reset by writing the value 0 to this
76 The record layout depends on the tracing mode set using the
80 Two tracing modes are implemented,
84 PC-tracing records a program counter value for each basic block executed while
85 tracing is enabled.
88 Comparison tracing provides information about data flow; information about
130 Set the size of the tracing buffer in units of
139 Enable coverage tracing for the calling thread.
[all …]
|
| H A D | dtrace_pid.4 | 11 .Nd a DTrace provider for dynamic userspace tracing based on function boundary instrumentation
21 provider implements userspace dynamic tracing
82 .Xr tracing 7
86 .%B DTrace: Dynamic Tracing in Oracle Solaris, Mac OS X and FreeBSD
92 .%B The illumos Dynamic Tracing Guide
|
| /freebsd/share/man/man7/ |
| H A D | tracing.7 | 10 .Nm tracing
11 .Nd introduction to FreeBSD tracing and performance monitoring
14 features a large variety of tracing and performance monitoring facilities.
22 is the most versatile tracing framework available on
24 and is capable of tracing throughout the
37 .Ss Userland Tracing
69 .Ss Kernel Tracing
76 .Ss Hardware-Accelerated Tracing
79 for hardware-assisted tracing.
87 .Ss Boot-Time And Shutdown Tracing
[all …]
|
| /freebsd/lib/libsys/ |
| H A D | ptrace.2 | 9 .Nd process tracing and debugging
21 provides tracing and debugging facilities.
24 .Em tracing
30 The tracing process must first attach to the traced process, and then
35 For the duration of the tracing session, the traced process will be
38 changed to the tracing process.
39 It is permissible for a tracing process to attach to more than one
41 When the tracing process has completed its work, it must detach the
42 traced process; if a tracing process exits without first detaching all
50 The tracing process is expected to notice this via
[all …]
|
| H A D | ktrace.2 | 33 .Nd process tracing
46 system call enables or disables tracing of one or more processes.
53 gives the pathname of the file to be used for tracing.
58 If tracing points are being disabled (see KTROP_CLEAR below),
71 .It KTROP_CLEARFILE Ta "Stop all tracing."
72 .It KTRFLAG_DESCEND Ta "The tracing change should apply to the"
97 .It KTRFAC_INHERIT Ta "Inherit tracing to future children."
100 Each tracing event outputs a record composed of a generic header
186 A thread may be unable to log one or more tracing events due to a
188 This condition is remembered by the kernel, and the next tracing request
|
| /freebsd/usr.bin/ktrace/ |
| H A D | ktrace.1 | 33 .Nd enable kernel process tracing
60 Once tracing is enabled on a process, trace data will be logged until
63 It is strongly suggested that users memorize how to disable tracing before
65 The following command is sufficient to disable tracing on all user-owned
83 Disable tracing on all user-owned processes, and, if executed by root, all
99 Enable (disable) tracing on all processes in the process group (only one
109 Enable (disable) tracing on the indicated process id (only one
173 .Sh CAPABILITY VIOLATION TRACING
199 Disable all tracing of process 65:
202 Disable tracing signals on process 70 and all current children:
[all …]
|
| /freebsd/share/man/man8/ |
| H A D | debug.sh.8 | 48 run-time tracing of complicated shell scripts.
51 turns tracing on if any
57 It turns tracing off if
66 that caused tracing to be enabled, or
79 option is present, tracing is turned off unless there
84 turns tracing on if any
110 returns true if tracing is enabled.
156 and if that does not turn tracing on,
181 If a function turns tracing on, ksh turns it off when the
|
| /freebsd/sys/dev/hwt/ |
| H A D | hwt.c | 32 * Hardware Tracing framework.
34 * The framework manages hardware tracing units that collect information
44 * calls to allow user to manage CPU (hardware) tracing units.
50 * Allocates kernel tracing context CTX based on requested mode
57 * Maps tracing buffers of the corresponding thread to userspace.
61 * Enables tracing unit for a given context.
82 * Some architectures may have different tracing units supported, so user
86 * it. Immediately, kernel initializes tracing backend.
92 * tracing for threads associated with the context (threads of the proc).
98 * 5. User mmaps tracing buffers of each thread to userspace (using
[all …]
|
| /freebsd/contrib/ncurses/man/ |
| H A D | curs_trace.3x | 114 \fBcurses_trace\fP, which selectively enables different tracing features, and
131 If tracing is available,
138 If the file already exists, no tracing is done.
140 If tracing is not available, \fBcurses_trace\fP returns zero (0).
147 turn off tracing by passing a zero parameter.
151 so that it can resume tracing later if a nonzero parameter is passed
202 Some tracing features are enabled whenever the \fBcurses_trace\fP parameter
222 If \fI\%ncurses\fP is built without tracing,
231 functions to enable the tracing feature as if
265 The SVr4 tracing feature is undocumented.
[all …]
|
| /freebsd/cddl/contrib/opensolaris/cmd/dtrace/test/tst/common/dtraceUtil/ |
| H A D | man.TraceFunctions | 47 * RESULT: tracing of matching list of probes with function read.
55 * RESULT: tracing of matching list of probes with function read.
63 * RESULT: tracing of probes with module genunix and function read.
67 * RESULT: tracing of probes with provider sysinfo, module genunix
72 * RESULT: tracing of probes with provider sysinfo and function read.
84 * RESULT: tracing of both read and write probes.
101 * RESULT: tracing of probes with function read and with message FOUND
105 * RESULT: tracing of probes with function read and with message FOUND
113 * RESULT: tracing of probes with function read, name entry and with
|
| H A D | man.TraceModule | 31 * Tracing a module using the -m option.
67 * RESULT: tracing of both genunix and unix probes.
84 * RESULT: tracing of all the probes matching provider fbt and module
89 * RESULT: tracing of all the probes matching module genunix with
94 * RESULT: tracing of all the probes matching module genunix with
112 * RESULT: tracing of all the probes matching module genunix,
|
| H A D | man.TraceNames | 71 * RESULT: tracing of probes with provider sysinfo, module genunix
76 * RESULT: tracing of probes with module genunix
84 * RESULT: tracing of probes with function read.
88 * RESULT: tracing of probes with provider profile and name
93 * RESULT: tracing of both read and write probes.
128 * RESULT: Tracing of BEGIN function but no message FOUND.
|
| /freebsd/sys/contrib/zstd/lib/common/ |
| H A D | zstd_trace.h | 43 /* Only enable tracing when weak symbols are available. */
104 * A tracing context. It must be 0 when tracing is disabled.
105 * Otherwise, any non-zero value returned by a tracing begin()
108 * Any non-zero value is treated as tracing is enabled and not
123 * @returns Non-zero if tracing is enabled. The return value is
132 * @param trace The zstd tracing info.
142 * @returns Non-zero if tracing is enabled. The return value is
151 * @param trace The zstd tracing info.
|
| /freebsd/contrib/llvm-project/lldb/include/lldb/Utility/ |
| H A D | TraceGDBRemotePackets.h | 44 /// Tracing technology name, e.g. intel-pt, arm-coresight.
47 /// If \a std::nullopt, then this starts tracing the whole process. Otherwise,
48 /// only tracing for the specified threads is enabled.
52 /// \b true if \a tids is \a std::nullopt, i.e. whole process tracing.
73 /// Tracing technology name, e.g. intel-pt, arm-coresight.
75 /// If \a std::nullopt, then this stops tracing the whole process. Otherwise,
76 /// only tracing for the specified threads is stopped.
89 /// Tracing technology name, e.g. intel-pt, arm-coresight.
150 /// Tracing technology name, e.g. intel-pt, arm-coresight.
|
| /freebsd/contrib/llvm-project/lldb/include/lldb/API/ |
| H A D | SBTrace.h | 68 /// Start tracing all current and future threads in a live process using a
69 /// provided configuration. This is referred as "process tracing" in the
92 /// Start tracing a specific thread in a live process using a provided
93 /// configuration. This is referred as "thread tracing" in the documentation.
97 /// If the thread is already being traced by a "process tracing" operation,
112 /// Stop tracing all threads in a live process.
114 /// If a "process tracing" operation is active, e.g. \a SBTrace::Start(const
124 /// Stop tracing a specific thread in a live process regardless of whether the
125 /// thread was traced explicitly or as part of a "process tracing" operation.
|
| /freebsd/sys/amd64/pt/ |
| H A D | pt.c | 13 * 'smp_rendezvous' to start and disable tracing on each target core.
16 * is generated for each 'pt_ctx' structure using the HWT tracing buffers.
17 * The HWT tracing buffer is split into 4K ToPA entries. Currently, each
23 * - When tracing starts, the PT hardware will start writing data into the
24 * tracing buffer. When a TOPA_INT entry is filled, it will trigger an
26 * last valid tracing buffer offset and enqueue a HWT_RECORD_BUFFER record.
29 * and uses the offsets to decode data from the tracing buffer.
34 * a 4K ToPA entry is filled. While this is fine when tracing smaller
36 * traffic when tracing hotter functions. A proper solution for this issue
40 * - Support for more tracing options and PT features.
[all …]
|
| /freebsd/libexec/rc/ |
| H A D | debug.sh | 22 # flexible run-time tracing of complicated shell scripts.
24 # DebugOn turns tracing on if any "tag" is found in "DEBUG_SH".
25 # It turns tracing off if "!tag" is found in "DEBUG_SH".
26 # It also sets "DEBUG_ON" to the "tag" that caused tracing to be
29 # If the '-o' flag is given, tracing is turned off unless there
37 # DebugOff turns tracing on if any "tag" matches "DEBUG_OFF" or
54 # Debugging returns true if tracing is enabled.
63 # Debug calls DebugOn and if that does not turn tracing on, it
76 # If a function turns tracing on, ksh turns it off when the
186 # Actually turn on tracing, set $DEBUG_ON=$match
[all …]
|
| /freebsd/crypto/openssl/include/openssl/ |
| H A D | trace.h | 75 * Enables tracing for the given |category| by providing a BIO sink
77 * trace channel is removed and tracing for the category is disabled.
96 * OSSL_trace_cb is the type tracing callback provided by the application.
116 * Enables tracing for the given |category| by creating an internal
119 * is removed and tracing for the category is disabled.
133 * Returns 1 if tracing for the specified category is enabled, otherwise 0
138 * Wrap a group of tracing output calls. OSSL_trace_begin() locks tracing and
140 * channel is associated with the category. OSSL_trace_end() unlocks tracing.
162 * When the tracing feature is disabled, these macros are defined to
233 * OSSL_TRACE_ENABLED() - Check whether tracing is enabled for |category|
|
| /freebsd/sys/kern/ |
| H A D | kern_boottrace.c | 47 static MALLOC_DEFINE(M_BOOTTRACE, "boottrace", "memory for boot tracing");
78 /* Boot-time tracing */
81 /* Run-time tracing */
84 /* Shutdown-time tracing */
87 /* Set when system boot is complete, and we've switched to runtime tracing. */
133 "Reset run-time tracing table");
141 "Boot-time and shutdown-time tracing enabled");
149 "Enable kernel shutdown tracing to the console");
158 "Tracing threshold (ms) below which tracing is ignored");
162 "Boot-time tracing table size");
[all …]
|
| /freebsd/cddl/contrib/opensolaris/cmd/dtrace/ |
| H A D | dtrace.1 | 28 .Nd dynamic tracing compiler and tracing utility
53 DTrace is a comprehensive dynamic tracing framework ported from Solaris.
72 Options that generate anonymous tracing programs
76 Options that modify DTrace tracing and buffering behavior and enable
137 Claim anonymous tracing state and display the traced data.
144 to exit immediately after consuming the anonymous tracing state rather than
147 Generate directives for anonymous tracing and write them to
150 the specified probes for anonymous tracing and then exits.
222 Exit after compiling any requests and consuming anonymous tracing state
227 option to print anonymous tracing data and exit.
[all …]
|