Table 2-20 lists the keywords for configuring the debugging options for a connection.
Keyword |
Value |
|---|---|
CS_DBG_FILE |
A character string specifying the destination file name for text-format debugging information. |
CS_DBG_PROTOCOL_FILE |
This ct_debug parameter may be set without devlib libraries. If the parameter is not set on connection, mktemp is called, generating a unique file name to dump the protocol packets into. The prefix string passed to mkstemp is capture. Ribo can decode the resulting protocol file. |
CS_PROTOCOL_FILE |
A character string specifying the destination file name for binary format debugging information. |
CS_DEBUG |
A character string giving a comma-separated list of debug flags. |
CS_DEBUG specifies the data to be written to the file CS_DBG_FILE. Its value can be a list of flags that correspond to the bitmasks for ct_debug’s flag parameter. For meanings of these debug flags, see “ct_debug”.
The possible flags are:
CS_DBG_ALL
CS_DBG_API_LOGCALL
CS_DBG_API_STATES
CS_DBG_ASYNC
CS_DBG_DIAG
CS_DBG_ERROR
CS_DBG_MEM
CS_DBG_NETWORK
CS_DBG_PROTOCOL
CS_DBG_PROTOCOL_FILE
CS_DBG_PROTOCOL_STATES
CS_DBG_SSL
