Debugging C++ Applications Using HP WDB (766162-001, March 2014)

Table 2 Summary of GDB Commands to Debug C++ Applications (continued)
PurposeGDB Command
Shows the current setting of overload resolution.
show overload-resolution
Prints static members when displaying a C++ object. The default is on.
Do not print static members when displaying a C++ object.
set print static-members [on |
off]
show print static-members
Sets enabling of namespace support. The default value is on.set namespaces-enabled [on |
off]
show namespaces-enabled
Enables or disables WDB to resolve opaque types. The default value is
on. A change in the setting of this subcommand does not take effect until
the next time symbols for a file are loaded.
set opaque-type-resolution [on
| off]
show opaque-type-resolution
Enables or disables printing of addresses. The default value is on. The
backtrace output also shows the value of program counter unless you
use the set print address off command.
set print address [on | off]
show print address
Instructs HP WDB to display only the symbolic form of an address if the
offset between the closest earlier symbol and the address is less than
set print max-symbolic-offset
<max-offset>
max-offset. The default is 0, which instructs HP WDB to always print
the symbolic form of an address if any symbol precedes it.
show print max-symbolic-offset
Limitations of using HP WDB to debug C++ applications
Following are the limitations of HP WDB when used for C++ debugging:
• Does not support command line call through ref-to-pointer.
• Does not support command line call through pointer-to-pointer.
• The operators dot(.) and hyphen with a greater than sign (->) can be
interchanged and used, which might be misleading sometimes.
• In case of function overloading, the disassemble and info address commands do not
provide the list.
• The WDB set print vtbl command, which is supposed to enable or disable printing of
virtual table when displaying value of structure or class object, is currently not available.
• Does not support mixed code debugging for Java/C/C++.
• WDB slows down when debugging C++ code with lot of templates.
• WDB does not make command line calls to string methods when there are no calls to these
methods from the application.
• WDB does not always evaluate overloaded operator in WDB expressions.
• WDB does not allow setting object-specific breakpoints.
• Catchpoints on exceptions are disabled within interactive calls.
• Exception cannot be raised interactively.
Documentation feedback
HP is committed to providing documentation that meets your needs. To help us improve the
documentation, send any errors, suggestions, or comments to Documentation Feedback
Limitations of using HP WDB to debug C++ applications 41