Launch configuration types

The IDE supports these default types of launch configurations:
C/C++ Application — (Run and Debug)
If you're developing non-QNX C/C++ projects, you can create this type of launch configuration to launch a program on the same (host) machine. You don't need to run qconn on the target in this case.
C/C++ Attach to Application — (Debug)
If you're developing non-QNX C/C++ projects, you can create this type of launch configuration to attach gdb to a running process. You don't need to use qconn; the IDE launches your program through gdb.
C/C++ Postmortem Debugger — (Debug)
This launch configuration comes directly from the Eclipse CDT, and requires extra steps to function correctly. Use the C/C++ QNX Postmortem Debugging configuration instead.
C/C++ QNX Attach to Remote Process via QConn (IP) — (Profile and Debug)
If you're connecting to your target machine through IP, select this configuration to attach to an existing remote process. This option lets you use the Application Profiler tool. Your target must be running qconn.
C/C++ QNX PDebug (Serial) — (Debug)
If you can access your target only through a serial connection, select this configuration. Rather than using qconn, the IDE uses the serial link capabilities of gdb directly.
C/C++ QNX Postmortem Debugging — (Debug)
If your program produced a dump file (with the dumper utility) when it crashed, you can examine the program's final state by loading the dump file into the debugger. When you start debugging, you're prompted to select a dump file.
C/C++ QNX QConn (IP) — (Profile, Run, and Debug)
Typically, you connect to your target machine over IP and should use this configuration type. You have full debugger control and can use the Application Profiler, Memory Analysis, Code Coverage, APS Options, and Kernel Logging tools. Your target must be running qconn.
Note: The main difference between this and other launch configuration types is that this type supports all of the runtime analysis tools.
C/C++ Remote Application — (Debug)
If you're developing non-QNX C/C++ projects, you can create this type of launch configuration to launch a program on a remote (target) machine. You don't need to run qconn on the target in this case.
GDB Hardware Debugging — (Debug)
Select this configuration if you want to connect to hardware debuggers that can integrate with GDB, such as JTAG devices. This launch configuration type also lets you specify:
  • Commands that get executed when GDB connects to the device
  • An image to load onto the target
  • Commands that configure the target
Launch Group — (Profile, Run, and Debug)
Lets you run multiple applications at the same time or in sequential order. Details about this launch configuration type are provided in the next section.