164
Chapter 20. Configuration-Specific Information
set new-group
mode
This boolean value controls whether the debuggee should start a new group or stay in the same
group as the debugger. This affects the way the Windows OS handles Ctrl-C.
show new-group
Displays current value of new-group boolean.
set debugevents
This boolean value adds debug output concerning events seen by the debugger.
set debugexec
This boolean value adds debug output concerning execute events seen by the debugger.
set debugexceptions
This boolean value adds debug ouptut concerning exception events seen by the debugger.
set debugmemory
This boolean value adds debug ouptut concerning memory events seen by the debugger.
set shell
This boolean values specifies whether the debuggee is called via a shell or directly (default value
is on).
show shell
Displays if the debuggee will be started with a shell.
20.1.4.1. Support for DLLs without debugging symbols
Very often on windows, some of the DLLs that your program relies on do not include symbolic
debugging information (for example,
kernel32.dll
). When gdb doesn’t recognize any debugging
symbols in a DLL, it relies on the minimal amount of symbolic information contained in the DLL’s
export table. This subsubsection describes working with such symbols, known internally to gdb as
"minimal symbols".
Note that before the debugged program has started execution, no DLLs will have been loaded. The
easiest way around this problem is simply to start the program -- either by setting a breakpoint or
letting the program run once to completion. It is also possible to force gdb to load a particular DLL
before starting the executable -- see the shared library information in (refer to Section 17.1
Commands
to specify files
or the
dll-symbols
command in (refer to Section 20.1.4
Features for Debugging
MS Windows PE executables
. Currently, explicitly loading symbols from a DLL with no debugging
information will cause the symbol names to be duplicated in gdb’s lookup table, which may adversely
affect symbol lookup performance.
20.1.4.2. DLL name prefixes
In keeping with the naming conventions used by the Microsoft debugging tools, DLL export symbols
are made available with a prefix based on the DLL name, for instance
KERNEL32!CreateFileA
.
The plain name is also entered into the symbol table, so
CreateFileA
is often sufficient. In some
cases there will be name clashes within a program (particularly if the executable itself includes full
debugging symbols) necessitating the use of the fully qualified name when referring to the contents
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: ......