Debugging with GDB (February 2008)

196 Debugging with GDB
• In the +std link mode, GDB supports this feature without any changes. You must
export the __wdb_call_dummy symbol as shown in the next line.
• In the +compat link mode, execute the following command:
cc +DD64-g file.c -Wl,+ee,__wdb_call_dummy -s
14.30.3 Support for debugging stripped binaries
HP WDB provides limited support for debugging stripped binaries.
14.30.3.1 Printing of locals and globals in a stripped module
GDB will not be able to print the locals and statics declared in a module which has
been stripped. GDB will be able to print the exported symbols since exported symbols
are not stripped with strip command (they stay in .dynsym).
GDB will be able to access the globals or locals defined in other unstripped shared
libraries loaded into the stripped executable when you are in the right scope.
14.30.3.2 Backtrace on stripped frames
GDB should be able to backtrace properly stripped frames. Arguments will not be
displayed (as in the case of non -g binary). If it is a fully archived stripped binary,
function names will not be displayed (but PCs will be).
14.30.3.3 Command line calls to non-stripped library
Command line calls to the functions (exported symbols) in the stripped binary work
fine. Command line calls to the non-stripped library work normally regardless where
the process is stopped.
14.30.3.4 Setting breakpoints in unstripped shared library
GDB will not be able to put breakpoints using symbolic names(of the symbols not in
export list) or line numbers in the stripped modules.
GDB will be able to place breakpoints using symbol names in the unstripped shared
libraries loaded into the stripped executable.
14.31 Displaying the current block scope information
The which command takes a symbol as an argument and prints the information on a
given symbol. It prints the following information:
• current block scope addresses
• line information of the definition of the symbol
• filename in which the definition of the symbol occurs