Create a log file

A profiling session usually involves the following steps:

To create a log file, you can gather trace events from the instrumented kernel in the following ways:


In order to get timing information from the kernel, you need to run tracelogger as the root user.

If you gather system-profiling data through qconn in the IDE, you're already accessing the instrumented kernel as root.

If you want to use the System Profiler to analyze the a log file generated by any of the methods indicated above, you must put the log file in an IDE project. It doesn’t matter how the log was created because the System Profiler can analyze the log from, for example, the tracelogger. The project is only a directory, so you can put the log file into any project, such as your QNX Target System Project, or a project relevant to your problem.

Using the command-line server currently offers more flexibility as to when the data is captured, but requires that you set up and configure filters yourself using the TraceEvent API. The Log Configuration dialog lets you set a variety of different static filters and configure the duration of time that the events are logged for.

For more information on the tracelogger utility, see its entry in the Utilities Reference. For traceevent , see the QNX Neutrino Library Reference.

When you chose which events to log, you may find that only some data is helpful to you. In many cases, only some types of events are relevant and you might need only a subset of the event information. As a result, you can have procnto-instr filter out some data, which will enable you to capture logs that are of a longer time duration, and it will improve system performance during the capture process itself. In addition, the reduction in data "noise" makes it easier for both you and the IDE to interpret the information.