To run and debug a program on your target system, you need to create a launch
configuration. It consists of various settings that affect how the program starts,
such as various parameters and environment variables. You enter these once, and then you can
use this collection of settings again and again.
The IDE supports these default types of launch configurations:
- C/C++ QNX QConn (IP) — (Profile, Run, and Debug)
- If you're connecting to your target machine by IP, select this configuration (even if
your host machine is also your target). You'll have full debugger control and can use the
Application Profiler, Memory Analysis, Code Coverage, Mudflap, APS
Options, and Kernel Logging tools. Your target must be running
qconn
. Typically, You'll likely be using this type of launch configuration.
- C/C++ Attach Local Application — (Debug)
- If you're developing non-QNX C/C++ programs, you may create a C/C++ Attach Local
Application launch configuration to attach gdb to the locally running
process. You don't need to use qconn; the IDE launches your program
through
gdb
.
- C/C++ Local Application — (Run and Debug)
- If you're developing non-QNX C/C++ projects, you may create a C/C++ Local launch
configuration. You don't need to use qconn; the IDE launches your
program through
gdb
.
- C/C++ Postmortem debugger — (Debug)
- If your program produced a dump file (via the
dumper
utility) when it faulted, you can examine the state of your program by loading it
into the postmortem debugger. This option is available only when you select
Debug. When you debug, you're prompted to select a dump file.
- C/C++ QNX Attach to Remote Process via QConn (IP) —
(Profile, Run, and Debug)
- If you're connecting to your target machine by IP, select this configuration to connect
to a remote process that is already running. This option lets you use the Application
Profiler tool for profiling. Your target must be running
qconn
.
- C/C++ QNX PDebug (Serial) — (Debug)
- If you can access your target only via a serial connection, select this configuration.
Rather than use qconn, the IDE uses the serial capabilities of
gdb
directly. This option is available only when you select
Debug.
- GDB Hardware Debugging — (Debug)
- If you want to connect to hardware debugging devices that support an integration with
GDB, such as JTAG. In addition, this launch configuration lets you specify:
- commands that get executed when GDB connects to the device
- an image to load on the target
- commands that configure the target for execution
- Launch Group — (Profile, Run, and Debug)
- Lets you run multiple applications at the same time or in sequential order. By default,
it runs in the mode that you selected when launching the application, and the IDE launches
the applications in the order that they appear in the Launches
list. You can specify a different target for each application; however, you must identify
the target separately in each individual launch configuration for the applications you
include in the list.
- PhAB Application
- If you wish to run a PhAB application, follow the steps for creating a
C/C++ QNX QConn (IP) launch configuration.
Note: In addition to these configurations, you can include other launch configuration types,
such as those for JTAG debugging. For general information about JTAG debugging, see
Use JTAG debugging.
The main difference between the C/C++ QNX QConn (IP) launch configurations and the other
types is that the C/C++ QNX QConn (IP) type supports the runtime analysis tools (QNX System
Profiler and the QNX Memory Trace).