[ < ] | [ > ] | [ << ] | [Plus haut] | [ >> ] | [Top] | [Table des matières] | [Index] | [ ? ] |
By default, the command gdb
starts GDB using a graphical interface,
using Emacs windows for display program state information. In effect, this
makes Emacs into an IDE (interactive development environment). With it, you
do not need to use textual GDB commands; you can control the debugging
session with the mouse. For example, you can click in the fringe of a
source buffer to set a breakpoint there, or on a stack frame in the stack
buffer to select that frame.
This mode requires telling GDB that its “screen size” is unlimited, so it sets the height and width accordingly. For correct operation you must not change these values during the GDB session.
You can also run GDB in text command mode, like other debuggers. To do
this, replace the GDB "--annotate=3"
option with "--fullname"
either in the minibuffer for the current Emacs session, or the custom
variable gud-gdb-command-name
for all future sessions. You need to
use text command mode to debug multiple programs within one Emacs session.
If you have customized gud-gdb-command-name
in this way, you can use
M-x gdba to invoke GDB in graphical mode.
32.6.5.1 GDB User Interface Layout | Control the number of displayed buffers. | |
32.6.5.2 Source Buffers | Use the mouse in the fringe/margin to control your program. | |
32.6.5.3 Breakpoints Buffer | A breakpoint control panel. | |
32.6.5.4 Stack Buffer | Select a frame from the call stack. | |
32.6.5.5 Other Buffers | Input/output, locals, registers, assembler, threads and memory buffers. | |
32.6.5.6 Watch Expressions | Monitor variable values in the speedbar. |
[ < ] | [ > ] | [ << ] | [Plus haut] | [ >> ] | [Top] | [Table des matières] | [Index] | [ ? ] |
Ce document a été généré par Eric Reinbold le 23 Février 2009 en utilisant texi2html 1.78.