Chapter 14. Using gdb with Different Languages
119
ptype
typename
Print inheritance relationships as well as other information for type
typename
. Refer to Chapter
15
Examining the Symbol Table
.
set print demangle
show print demangle
set print asm-demangle
show print asm-demangle
Control whether C
++
symbols display in their source form, both when displaying code as C
++
source and when displaying disassemblies. Refer to Section 10.7
Print settings
.
set print object
show print object
Choose whether to print derived (actual) or declared types of objects. Refer to Section 10.7
settings
.
set print vtbl
show print vtbl
Control the format for printing virtual function tables. Refer to Section 10.7
Print settings
. (The
vtbl
commands do not work on programs compiled with the HP ANSI C
++
compiler (
aCC
).)
set overload-resolution on
Enable overload resolution for C
++
expression evaluation. The default is on. For overloaded
functions, gdb evaluates the arguments and searches for a function whose signature matches the
argument types, using the standard C
++
conversion rules ((refer to Section 14.4.1.3
C++expressions
, for details). If it cannot find a match, it emits a message.
set overload-resolution off
Disable overload resolution for C
++
expression evaluation. For overloaded functions that are
not class member functions, gdb chooses the first function of the specified name that it finds in
the symbol table, whether or not its arguments are of the correct type. For overloaded functions
that are class member functions, gdb searches for a function whose signature
exactly
matches the
argument types.
Overloaded symbol names
You can specify a particular definition of an overloaded symbol, using the same notation that is
used to declare such symbols in C
++
: type
symbol
(
types
)
rather than just
symbol
. You can
also use the gdb command-line word completion facilities to list the available choices, or to finish
the type list for you. Refer to Section 5.2
Command completion
, for details on how to do this.
14.4.2. Objective-C
This section provides information about some commands and command options that are useful for
debugging Objective-C code.
14.4.2.1. Method Names in Commands
The following commands have been extended to accept Objective-C method names as line specifica-
tions:
Summary of Contents for ENTERPRISE LINUX 4 - DEVELOPER TOOLS GUIDE
Page 1: ...Red Hat Enterprise Linux 4 Debugging with gdb ...
Page 12: ...2 Chapter 1 Debugging with gdb ...
Page 28: ...18 Chapter 4 Getting In and Out of gdb ...
Page 34: ...24 Chapter 5 gdb Commands ...
Page 44: ...34 Chapter 6 Running Programs Under gdb ...
Page 68: ...58 Chapter 8 Examining the Stack ...
Page 98: ...88 Chapter 10 Examining Data ...
Page 112: ...102 Chapter 12 Tracepoints ...
Page 118: ...108 Chapter 13 Debugging Programs That Use Overlays ...
Page 138: ...128 Chapter 14 Using gdb with Different Languages ...
Page 144: ...134 Chapter 15 Examining the Symbol Table ...
Page 170: ...160 Chapter 19 Debugging remote programs ...
Page 198: ...188 Chapter 21 Controlling gdb ...
Page 204: ...194 Chapter 22 Canned Sequences of Commands ...
Page 206: ...196 Chapter 23 Command Interpreters ...
Page 216: ...206 Chapter 25 Using gdb under gnu Emacs ...
Page 296: ...286 Chapter 27 gdb Annotations ...
Page 300: ...290 Chapter 28 Reporting Bugs in gdb ...
Page 322: ...312 Chapter 30 Using History Interactively ...
Page 362: ...352 Appendix D gdb Remote Serial Protocol ...
Page 380: ...370 Appendix F GNU GENERAL PUBLIC LICENSE ...
Page 386: ...376 Appendix G GNU Free Documentation License ...
Page 410: ......