GDB expression handling can interpret most C++ expressions.
Warning: GDB can only debug C++ code if you use the proper compiler. Typically, C++ debugging depends on the use of additional debugging information in the symbol table, and thus requires special support. In particular, if your compiler generates a.out, MIPS ECOFF, RS/6000 XCOFF, or ELF with stabs extensions to the symbol table, these facilities are all available. (With GNU CC, you can use the `-gstabs' option to request stabs debugging extensions explicitly.) Where the object code format is standard COFF or DWARF in ELF, on the other hand, most of the C++ support in GDB does not work.
count = aml->GetOriginal(x, y)
thisfollowing the same rules as C++.
set overload-resolution off. See section GDB features for C++. You must specify
set overload-resolution offin order to use an explicit function signature to call an overloaded function, as in
p 'foo(char,int)'('x', 13)The GDB command-completion facility can simplify this; see section Command completion.
::---your expressions can use it just as expressions in your program do. Since one scope may be defined in another, you can use
::repeatedly if necessary, for example in an expression like `scope1::scope2::name'. GDB also allows resolving name scope by reference to source files, in both C and C++ debugging (see section Program variables).
In addition, when used with HP's C++ compiler, GDB supports calling virtual functions correctly, printing out virtual bases of objects, calling functions in a base subobject, casting objects, and invoking user-defined operators.
Go to the first, previous, next, last section, table of contents.