Lines Matching refs:In
78 In addition it supports various export functionalities that allow you to analyze
86 has been started. In order to break as little as possible in existing code to
89 tracing framework. In the end the structure of the trace logs that are generated
93 In this section we want to look at the part of the tracing framework that is
137 also be extended, a possible idea would be to store the trace log in a file. In
168 In addition to the Subsystem, Event and Argument information, the tracing
211 \ref{lst:pleco-file}. In this file we define two Subsystems: \texttt{kernel} and
263 Listing \ref{lst:headerfile} has been generated during the build process. In
406 triggered by manually calling the according trace framework function. In
477 visualization code for custom developer scripts. In Section \ref{sec:scripts} we
556 especially handy when considering the filtering functionality of Aquarium. In
609 Aquarium. In Figure \ref{fig:classdiag-output} we can see that such a Script is
620 In this section we briefly want to look at how some of the already described
631 well in the left menu labeled \emph{Filter}. In addition to the per core events,
670 In Figure \ref{fig:aquarium-filters} we activated several filters, thus compared
797 In addition to those buffers, a handful of pointers are stored, which in total