Common Desktop Environment: ToolTalk Messaging Overview

Settings for ToolTalk Tracing

A ttrace script contains settings that control ToolTalk calls and messages. A ttrace script consists of commands separated by semicolons or newlines. If conflicting values are given for a setting, the last value is the one used. Table 4-5 describes these commands.

Table 4-5 tttrace Script Commands


Command	Description
`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 shell interpretation of > and >> applies.
`functions` [all \| none \| `func`...]	ToolTalk API functions to trace. `func` may include shell wildcard characters. Default is `all`.
`attributes [all \| none]`	`none` (default) 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.
`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 plus all patterns considered for matching (default).
`ops` `toTrace`... `sender_ptypes` `toTrace`... `handler_ptypes` `toTrace`...	Trace messages that have `toTrace` as a value for the indicated message attribute. `toTrace` may include shell wildcard characters. If no `toTrace` argument is included for a given message attribute, then no value of that attribute excludes a message from tracing.