JTAG Debugging: There is a new debug launch configuration to support GDB
Hardware Debug through the JTAG interface. There is built-in support for the
Abatron BDI2000 and Macraigor USB2Demon JTAG devices, with other device
support, such as the Lauterbach Trace32 In-Circuit Debugger, through
self-defined hardware specific command sets. For more information about JTag
debugging, see Using JTAG debugging.
Added the View Memory feature in the Variable view
that lets you see a variable in memory. For information about this feature,
see Inspecting variables.
In the Launch Configuration, the Debug tab was
updated for QNX Qconn and QNX
Pdebug launches to include a debugger selection
box and a verbose mode option. Verbose console mode
shows the details of the interaction with the command line debugger in the
gdb process console. This option can be enabled from launch
configuration, or by right-clicking on the process in the Debug view. For
additional information about these features, see Debugger tab.
You can also set breakpoint actions directly from the Breakpoint view using
a new GDB breakpoints actions page called GDB Command
Action. This features lets you specify GDB commands; one
command per line. You can define a GDB command action, and attach it to one
or more breakpoints. When the IDE encounters a breakpoint, the defined GDB
command(s) will run, and the result shows in the GDB console. There is also
a new global preference GDB Command Action page that
you can access by selecting Windows
> Preferences
> C/C++
> Debug
> Breakpoint Actions. This preference page lets you define one of more reusable
GDB command actions that you can attach to a breakpoint at a later time. For
more information, see Adding breakpoints.
For the source locator, an absolute path mapping entry was added to the
global preferences (Windows
> Preferences
> C/C++
> Debug
> Common Source Lookup Path). This means that for a large project that is compiled on the
same host as the IDE runs, it will use this location instead of the default
source location specified on the Source tab in the
Launch configuration.
On the Debug tab for a Launch Configuration, there
is a new option, called Use full path to set
breakpoints, that lets you set breakpoints using the full
file name. If you have many files with the same base name in the project,
selecting this option is the preferred method of setting breakpoints. For
additional information, see Debugger tab.
The IDE now lets you edit the line number for a breakpoint. Right-click on
the breakpoint, select Properties, select the
Common tab, and then edit the line number. In
addition, you can also move the line number of the existing breakpoint. To
show line numbers in an editor, select the Show line
numbers option from Window
> Preferences
> General
> Editors
> Text Editors.
Added support for GDB catchpoints such that you can set event breakpoints
for these types of events: exception caught and exception thrown. For more
information, see Using breakpoints and watchpoints.
Corrections:
Note: For additional information about the corrections that were made
to the IDE, see List of fixes in the Release Notes.
Addressed a problem with the UI being deadlocked, and debugger UI being
unresponsive during the launch, and in some other situations.
Hardcoded timeouts for a suspend operation have been fixed such that the
default MI command timeout will be used. This command is user
configurable.
When an error occurs during a launch, the IDE is now able to successfully
close unresponsive debug sessions.
Fixed a problem where, in some situations, the debugger was encountering
disabled breakpoints, and not being able to encounter enabled ones.
You can now view base class members in the Variables view.
Fixed the shared library loading for gdb version 6.7.
When a breakpoint is set from the gdb console using an address, you
can now successfully navigate to the breakpoint source code.
Fixed postmortem debugging in that you can now pass the user defined shared
libraries path to the debugger. In addition, there are also some corrections
to gdb where the IDE now supports gdb 6.7 update 5 or
higher.