Caution: This version of this document is no longer maintained. For the latest documentation, see

Testing and Debugging

This chapter includes:

Instrumented kernel trace events

The instrumented kernel emits trace events when:

In addition, all events include the scheduler partition ID and its budget. You can use traceprinter to display the contents of the trace file. You can also use the QNX IDE to parse and display a trace file.

Using the QNX IDE (trace events)

You can—and should—use the System Profiler tool from the QNX IDE to check your system's latencies. For more information about using this tool and the IDE, see the IDE User's Guide.

Using other methods

The easiest method to test a system that uses the thread scheduler is from the command line.

Be sure to test your system in a fully loaded state, because that's where problems are likely to occur. Create a program that consumes resources by looping forever, run it in each partition, and then do the following:

Emergency access to the system

You can use adaptive partitioning to make it easier to debug an embedded system by providing emergency access to it:

In either case, if you don't need to use this partition, the thread scheduler allocates its budget among the other partitions. This provides you with emergency access to the system without compromising performance.