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.
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.

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.
- 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 server

Updated: November 27, 2023

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.

The QNX Toolkit System Profiler includes the VS Code trace extension and QNX Trace Server:

The VS Code trace extension provides the various views, actions, and graphs.
The QNX Trace Server communicates with the trace extension to parse, filter, and provide the data for visualization.

CAUTION: A running trace server is indicated by the green icon at the bottom right of VS Code (

). You need to have a running trace server to view the trace files.