TTTRACEFILE(4)

✨ NAME ✨

tttracefile — script of settings for ToolTalk tracing. Okay so this is the tttracefile(special file) manual page, bestie, and it's literally giving “tiny config script that tells ToolTalk what to trace” main character energy. 💅

---

🦋 SYNOPSIS 🦋

tttracefile

💖 DESCRIPTION 💖

A tttrace script contains settings that control ToolTalk calls and messages. A tttrace script consists of commands separated by semicolons or newlines. The first command must be the version command — like, no cap, it has to open the show. ✨

🎀 Commands 🎀

If conflicting values are given for a setting, the last value wins — that's the vibe check. 💅

• version n — the version of the tttracefile command syntax used. The current version is 1.
• follow [off | on] — sets whether to follow all children forked by the traced client or subsequently started in the traced session. Default is off.
• [> | >>] outfile — file to be used for the trace output. By default, trace output goes to standard error. Normal sh(1) interpretation of > and >> applies.
• functions [all | none | func...] — ToolTalk API functions to trace. func may include sh(1) wildcard characters. Default is all.
• attributes [all | none] — none means use only a single line when printing a message on the trace output. all means print all attributes, arguments, and context slots of traced messages. Default is none.
• states [none | edge | deliver | dispatch | Tt_state]... — state(s) through which to trace messages. In addition to the Tt_states defined in tt_c.h, valid states are:
  • none — disable all message tracing
  • edge — messages entering initial (TT_SENT) and final (TT_HANDLED, TT_FAILED) states.
  • deliver — all state changes and all client deliveries.
  • dispatch — deliver + all patterns considered for matching. (default)
• ops toTrace... — trace messages that have toTrace as a value for the indicated message attribute.
• sender_ptypes toTrace... — trace messages that have toTrace as a value for the indicated message attribute.
• handler_ptypes toTrace... — trace messages that have toTrace as a value for the indicated message attribute.

For those three: toTrace may include sh(1) wildcard characters. If no toTrace argument is included for a given message attribute, then no value of that attribute excludes a message from tracing.

🩷 Comments 🩷

A word beginning with # causes that word and all the following characters up to a newline to be ignored. Iconic comment behavior, honestly. 🫶

🌈 EXAMPLES 🌈

To trace all attribute-getting and -setting messages sent by ptype starting with "Dt":

version 1 ops Get* Set* sender_ptypes Dt*

To trace only ToolTalk function calls (but not messages) in a process tree:

version 1; follow on; states none

💜 SEE ALSO 💜

ttsession(1), tttrace(1), the Session_Trace() ToolTalk request. Go read those too, iykyk. 🦋

---

💖 That's the whole page, bestie! Footer sign-off: the source/version line is tttracefile(special file) — and there's literally no date printed on this page, so I'm not inventing one, periodt. 🫶