diff options
author | Nathan Day <nathandotday98@gmail.com> | 2021-12-04 20:26:17 +0300 |
---|---|---|
committer | Nathan Day <nathandotday98@gmail.com> | 2021-12-04 20:26:17 +0300 |
commit | 3bf1e7ec1c348176580d0898357bccb020c34337 (patch) | |
tree | 6a93f331c7ac80608369d43320376aaaae602f98 /manual | |
parent | bdafd0c7b6e2c26cfb0fb957506de4aa18a4943e (diff) |
Updated documentation
Diffstat (limited to 'manual')
-rw-r--r-- | manual/tracy.tex | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/manual/tracy.tex b/manual/tracy.tex index dd17f49b..f15e0cec 100644 --- a/manual/tracy.tex +++ b/manual/tracy.tex @@ -1862,6 +1862,10 @@ To see how this API should be used you should look at the reference implementati Fibers are available in the C API through the \texttt{TracyCFiberEnter} and \texttt{TracyCFiberLeave} macros. To use them, you should observe the requirements listed in section~\ref{fibers}. +\subsubsection{Connection Status} + +To query the connection status (section~\ref{connectionstatus}) using the C API you should use the TracyCIsConnected macro. + \subsubsection{Call stacks} You can collect call stacks of zones and memory allocation events, as described in section~\ref{collectingcallstacks}, by using macros with \texttt{S} postfix, such as: \texttt{TracyCZoneS}, \texttt{TracyCZoneNS}, \texttt{TracyCZoneCS}, \texttt{TracyCZoneNCS}, \texttt{TracyCAllocS}, \texttt{TracyCFreeS}, and so on. @@ -2086,6 +2090,7 @@ Usage of trace parameters makes profiling runs dependent on user interaction wit \end{bclogo} \subsection{Connection status} +\label{connectionstatus} To determine if a connection is currently established between the client and the server, you may use the \texttt{TracyIsConnected} macro, which returns a boolean value. |