Home
QNX Toolkit for Visual Studio Code
This User's Guide describes the QNX Toolkit for Visual Studio Code. The guide introduces you to the QNX Toolkit by explaining the QNX development environment and how to build, run, and debug your QNX OS applications and systems.
Using the System Profiler
You can use the System Profiler to render different types of trace analysis, such as graphs and tables.
Analysis views
The QNX Toolkit System Profiler displays kernel event trace data. You can view different aspects of the application's activity and examine events within a specific time range in detail. There are also several views that list helpful information such as the Histogram, Timeline View, and CPU Usage View.
Trace Properties view
This view enables you to view the properties of the trace.kev file.

QNX Toolkit for Visual Studio Code
This User's Guide describes the QNX Toolkit for Visual Studio Code. The guide introduces you to the QNX Toolkit by explaining the QNX development environment and how to build, run, and debug your QNX OS applications and systems.
- About the QNX Toolkit
- Using the Target Navigator
  The QNX development environment consists of a host and a target machine.
- Developing QNX Projects
  To use the QNX Toolkit to write applications targeted for QNX OS systems, you must define projects, which are folders in the filesystem. A VS Code workspace is a collection of these folders and VS Code settings defined by the .code-workspace file. QNX projects are saved to a folder defined in a your configuration (default location is ~/qnxprojects).
- Debugging and Launching
- Using the System Profiler
  You can use the System Profiler to render different types of trace analysis, such as graphs and tables.
  - Initiating kernel logging
    You can use kernel logging on a selected target. When you run the logging command, QNX Toolkit attempts to find a launch configuration for the selected target in the currently active Workspace. If none is found, then it creates the default launch configuration and runs it.
  - Managing traces
    Opening a trace file starts the Trace Server and opens the System Profiler.
  - Trace server
    The Trace Server is the heart of the QNX System Profiler. It includes state systems, analysis modules and data providers for the .kev (kernel event) tracing format that the System Profiler uses for its views.
  - Analysis views
    The QNX Toolkit System Profiler displays kernel event trace data. You can view different aspects of the application's activity and examine events within a specific time range in detail. There are also several views that list helpful information such as the Histogram, Timeline View, and CPU Usage View.
    - Events Table view
      The Events Table view displays the raw events in table form. When you select an area of the Overview graph, the Events Table updates to reflect the chosen data.
    - Timeline view
      The Timeline view shows the chronology of the logged kernel events of a trace.kev file. Hover over the color bands to display relevant information.
    - CPU Usage View
      You can use the CPU Usage View to display recorded CPU usage statistics. You can filter the statistics by CPUs and owners.
    - Trace Properties view
      This view enables you to view the properties of the trace.kev file.
    - Histogram view
      The Histogram shows the number of events in time for a trace. This is the default view for the System Profiler.
    - Owner and event filters
      Using the filters, you can restrict which owners and events are represented in the Events Table and Timeline View.
- References
  The reference topics provide information about QNX Toolkit features and workflows that isn't covered in the other chapters.
- Glossary
  To make best use of the QNX Toolkit, we recommend that you become familiar with the following terms, which are used throughout the user interface and documentation.
- Typographical Conventions, Support, and Licensing
  This section describes the typographical conventions used throughout the documentation and explains how to obtain technical support.

Trace Properties view

Updated: November 27, 2023

This view enables you to view the properties of the trace.kev file.

Creating the view

With a running trace server and trace compass extension, the Trace Properties View is available from the Views panel in the System Profiler.

To create the view:

Click Trace Properties View in the Views panel of the Trace Server.
The table of properties is displayed.

The available types are as follows:


Key	`Value`
Calculated
Total Log File Time	The total time span covered by the trace log.
Total Number of Events	The count of individual events captured in the trace log.
Dropped buffers	The number of event buffers that were not recorded due to buffer overflow or other reasons.
Number of CPUs	Number of CPUs.
Busy time	The cumulative time during which the CPU was actively processing tasks.
Idle time	The cumulative time during which the CPU was not actively processing tasks.
Static
BOOT_DATE	The system's boot date and time.
CPU_NUM	The number of CPUs on the system.
CYCLES_PER_SEC	The number of clock cycles per second for the CPU.
DATE	The date and time when the trace was captured.
ENCODING	The size of each event entry in the trace.
FILE_NAME	The path to the trace file.
LITTLE_ENDIAN	The endianness of the system.
MACHINE	The type of machine or architecture.
NODENAME	The network name of the machine.
NORMALIZEDN	Numerical value that indicates that the trace was normalized by IDE.
SYSNAME	The operating system name.
SYSPAGE_LEN	The length of the system page.
SYS_RELEASE	The release version of the operating system.
SYS_VERSION	The build date and time of the operating system.
TRACELOGGER_ARGS	Tracelogger arguments.
VER_MAJOR	The major version number of the trace system.
VER_MINOR	The minor version number of the trace system.