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^® Operating System (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.
Properties
The PROPERTIES list shows you high level information regarding the .kev file under analysis.

QNX Momentics IDE User's Guide
This User's Guide describes version 8.0 of the Integrated Development Environment (IDE) that's part of the QNX Tool Suite.
QNX Software Development Platform
QNX SDP is a cross-compiling and debugging environment, including an IDE and command-line tools, for building binary images and programs for target boards running the QNX OS 8.0.
QNX Software in the Cloud
QNX Software in the Cloud enables developers to use the QNX software in Amazon Web Services (AWS) and Microsoft Azure (Azure).
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^® Operating System (OS) applications and systems.
- About the QNX Toolkit
  The QNX Toolkit for the Visual Studio Code provides VS Code users with access to the world-class POSIX-based QNX development environment.
- Using the Target Navigator
  The QNX development environment consists of a host and a target machine.
- Developing QNX Projects
  The QNX Toolkit contains wizards for creating projects based on specific programming languages.
- Debugging and Launching
  The QNX Toolkit allows you to debug or run an application remotely on a QNX target.
- 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 System Profiler and displays its dashboard 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 Timeline and CPU Usage view.
  - Properties
    The PROPERTIES list shows you high level information regarding the .kev file under analysis.
  - Filtering traces
    Using the filters, you can globally restrict which owners and events are displayed in the System Profiler dashboard views.
- References
  The reference topics provide information about QNX Toolkit features and workflows that aren't covered in the other chapters.
- Tutorials
  Tutorials aim to help you understand how to use QNX Toolkit with your own applications by providing step-by-step guides.
- 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.
QNX Hypervisor User's Guide
This User's Guide explains the QNX hypervisor architecture and provides instructions for installing and running a QNX Hypervisor system, changing system components and configuration, and using hypervisor features such as virtual devices (vdevs).
Typographical Conventions, Support, and Licensing
This section describes the typographical conventions used throughout the documentation, explains how to obtain technical support, and provides some information about licensing.

Properties

QNX Toolkit1.1QNX Toolkit User's GuideDeveloperSetup

The PROPERTIES list shows you high level information regarding the .kev file under analysis.

Opening the view

You can display the trace properties by expanding PROPERTIES in the System Profiler.

To open the view:

Click QNX SYSTEM PROFILER, then select a .kev file.
Click PROPERTIES.
The properties of the trace are displayed:

The available types are as follows:


Key	Description
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.
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.
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; true for little endian and false for big endian.
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.

Page updated: September 22, 2025