Debugging with GDB Manual (5900-1473; WDB 6.2; January 2011)

discard symbols when linking
large programs, that may
contain several modules
(from different directories or
libraries) with the same
name.
show
symbol-reloading
Show the current on or off
setting.
set opaque-type-resolution
on
Tell GDB to resolve opaque types. An opaque
type is a type declared as a pointer to a struct,
class, or union―for example, struct
MyType *―that is used in one source file
although the full declaration of struct MyType
is in another source file. The default is on.
A change in the setting of this subcommand will
not take effect until the next time symbols for a file
are loaded.
set opaque-type-resolution
off
Tell GDB not to resolve opaque types. In this case,
the type is printed as follows:
{<no data fields>}
show opaque-type-resolution Show whether opaque types are resolved or not.
maint print symbols
filename, maint print
Write a dump of debugging symbol data into the
file filename. These commands are used to
debug the GDB symbol-reading code. Only
psymbols filename, maint
print msymbols filename
symbols with debugging data are included. If you
use 'maint print symbols', GDB includes all
the symbols for which it has already collected full
details: that is, filename reflects symbols for
only those files whose symbols GDB has read.
You can use the command info sources to
find out which files these are. If you use 'maint
print psymbols' instead, the dump shows
information about symbols that GDB only knows
partially―that is, symbols defined in files that GDB
has skimmed, but not yet read completely. Finally,
'maint print msymbols' dumps just the
minimal symbol information required for each
object file from which GDB has read some
symbols. See “Commands to specify files”
111