The Debugger tab lets you configure how your debugger works.
Note:
To debug your application, you must
build its executable for debugging.
Also, the Debugger tab settings affect your executable only when you debug it, not when you run it.
Generic debugger settings
- Debugger
- The debugger dropdown lists the available debuggers for the selected launch configuration type.
The list also varies depending on whether you're debugging a remote or a local target.
-
Stop on startup at
- By default, this option is selected and the default location is
main. If you deselect it, the program runs until you
interrupt it manually, or until it encounters a breakpoint.
-
Advanced
- Clicking this button opens the Advanced Options dialog, which lets you check and uncheck the
Variables and Registers boxes.
Check these boxes if you want the system to track every variable and register as you step through
your program. Uncheck Variables to manually select individual variables
to work with in the Variables view in the debugger. Unchecking Registers
works the same way for the Registers View.
Note: If you choose to track all variables or registers, your program's performance may decrease.
Debugger options
The
Main and
Shared libraries tabs let
you specify options for the debugger that you selected. These options include but aren't limited to:
- GDB debugger
-
Specify the GDB version to use. The default value of gdb means the IDE selects the version based on the
architecture of the executable. The IDE comes with several GDB versions, each of which is named based on its supported
architecture (e.g., ntoarmv7-gdb).
Information on the debugger is given in the gdb entry in the QNX Neutrino Utilities Reference.
-
The only time you might want to change this field is if you're running a different gdb binary
(e.g., a patched version) or if the IDE fails to pick the correct debugger version.
- GDB command file
-
Specify the path of a file containing commands to be executed by GDB.
When you fill in this field, the IDE runs gdb with the -command option
and uses the specified command file as that option's value. The default path is .gdbinit.
-
Verbose console mode
- See all of the commands sent to GDB, and all of the responses returned from GDB.
-
Use full path to set breakpoints
- Set breakpoints if you have many files with the same base name in the project.
When file names are identical but their paths are different, setting this option
ensures that breakpoints are set for the appropriate file, as expected.
-
Load shared library symbols automatically
- Watch line-by-line stepping of library functions in the C/C++ editor. You may
want to deselect this option if your target doesn't have much memory; the
library symbols consume RAM on the target.
-
Stop on shared library events
- Choose this option to make the debugger break automatically when a shared library or DLL is loaded or unloaded.