GNU调试器GDB使用手册

需积分: 0 167 浏览量更新于2024-08-02 收藏 1.75MB PDF 举报

身份认证购VIP最低享 7 折!

30元优惠券

“Debugging with gdb - The GNU Source-Level Debugger Ninth Edition for gdb version 7.0.50.20090924” 本文档是关于GNU调试器（GDB）的详细指南，适用于版本7.0.50.20090924。GDB是一个强大的开源工具，主要用于调试C、C++和其他编程语言编写的程序。通过GDB，开发者可以在运行时检查代码状态，包括变量值、内存分配、调用堆栈等，帮助识别和修复程序中的错误。 1. **GDB基础** - **启动GDB**：你可以通过命令行界面启动GDB，并加载目标程序进行调试。 - **设置断点**：在程序的特定位置设置断点，使得程序在执行到这些点时暂停，便于检查当时的运行状态。 - **单步执行**：GDB允许你逐行执行代码，查看每一步的结果。 - **查看变量**：可以随时查看变量的当前值，了解程序运行过程中的数据变化。 - **堆栈跟踪**：查看调用堆栈，理解函数调用关系和执行路径。 2. **GDB高级特性** - **条件断点**：断点可以附加条件，只有满足特定条件时才会触发。 - **Watchpoints**：监视特定变量或内存地址，当其值发生变化时暂停程序。 - **命令脚本**：编写GDB命令脚本，自动化调试流程，提高效率。 - **远程调试**：通过网络连接远程调试目标系统上的程序。 - **多线程调试**：支持同时调试多个线程，查看并控制每个线程的状态。 3. **GDB与源码** - **源码级调试**：GDB能够与源码结合，提供清晰的代码视图，便于理解程序执行逻辑。 - **符号表**：GDB读取程序的符号表信息，用于解析变量名、函数名等。 4. **调试技巧** - **逆向执行**：在某些情况下，GDB可以允许你反向执行代码，回溯到某个状态。 - **内存查看**：检查和修改程序运行时的内存，查找内存泄漏或异常访问问题。 - **核心转储分析**：当程序崩溃时，可以生成核心转储文件，GDB可以用来分析这个文件，找出崩溃原因。 5. **GDB与开发环境集成** - **IDE集成**：许多集成开发环境（IDE）如Eclipse、Visual Studio Code等支持GDB作为其内置调试器。 - **GDB服务器**：配合GDB服务器，可以在一个环境中控制远程设备上的调试过程。 6. **GDB扩展与自定义** - **Python脚本**：GDB可以通过Python API扩展功能，创建自定义的命令和插件。 - **第三方增强**：社区提供了如GDBMI（GDB Machine Interface）等增强工具，改进交互方式和输出格式。 7. **许可证与贡献** GDB遵循GNU Free Documentation License，允许自由复制、分发和修改文档。用户可以对GDB提出问题和建议，通过指定网址（http://www.gnu.org/software/gdb/bugs/）报告bug和提供反馈。 GDB是开发者不可或缺的工具，无论你是初学者还是经验丰富的程序员，都可以通过深入学习GDB来提升你的调试技能，更好地理解和优化你的代码。

资源详情

资源推荐

Chapter 2: Getting In and Out of gdb 11

2 Getting In and Out of gdb

This chapter discusse s how to start gdb, and how to get out of it. The essentials are:

• type ‘gdb’ to start gdb.

• type quit or Ctrl-d to exit.

2.1 Invoking gdb

Invoke gdb by running the program gdb. Once started, gdb reads commands from the

terminal until you tell it to exit.

You can also run gdb with a variety of arguments and options, to specify more of your

debugging environment at the outset.

The command-line options described here are designed to cover a variety of situations;

in some environments, some of these options may eﬀectively be unavailable.

The most usual way to start gdb is with one argument, specifying an executable program:

gdb program

You can also start with both an executable program and a core ﬁle speciﬁed:

gdb program core

You can, instead, specify a process ID as a second argument, if you want to debug a

running process:

gdb program 1234

would attach gdb to process 1234 (unless you also have a ﬁle named ‘1234’; gdb does check

for a core ﬁle ﬁrst).

Taking advantage of the second command-line argument requires a fairly complete op-

erating system; when you use gdb as a remote debugger attached to a bare board, there

may not be any notion of “process”, and there is often no way to get a core dump. gdb

will warn you if it is unable to attach or to read core dumps.

You can optionally have gdb pass any arguments after the executable ﬁle to the inferior

using --args. This option stops option processing.

gdb --args gcc -O2 -c foo.c

This will cause gdb to debug gcc, and to set gcc’s command-line arguments (see hunde-

ﬁnedi [Arguments], page hundeﬁnedi) to ‘-O2 -c foo.c’.

You can run gdb without printing the front material, which describes gdb’s

non-warranty, by specifying -silent:

gdb -silent

You can further control how gdb starts up by using command-line options. gdb itself can

remind you of the options available.

Type

gdb -help

to display all available options and brieﬂy describe their use (‘gdb -h’ is a shorter equiva-

lent).

All options and command line arguments you give are processed in sequential order. The

order makes a diﬀerence when the ‘-x’ option is used.

12 Debugging with gdb

2.1.1 Choosing Files

When gdb starts, it reads any arguments other than options as specifying an executable

ﬁle and core ﬁle (or process ID). This is the same as if the arguments were speciﬁed by the

‘-se’ and ‘-c’ (or ‘-p’) options respectively. (gdb reads the ﬁrst argument that does not

have an associated option ﬂag as equivalent to the ‘-se’ option followed by that argument;

and the second argument that does not have an associated option ﬂag, if any, as equivalent

to the ‘-c’/‘-p’ option followed by that argument.) If the second argument begins with a

decimal digit, gdb will ﬁrst attempt to attach to it as a process, and if that fails, attempt

to open it as a coreﬁle. If you have a coreﬁle whose name begins with a digit, you can

prevent gdb from treating it as a pid by preﬁxing it with ‘./’, e.g. ‘./12345’.

If gdb has not been conﬁgured to included core ﬁle support, such as for most embedded

targets, then it w ill complain about a second argument and ignore it.

Many options have both long and short forms; both are shown in the following list. gdb

also recognizes the long forms if you truncate them, so long as enough of the option is

present to be unambiguous. (If you prefer, you can ﬂag option arguments with ‘--’ rather

than ‘-’, though we illustrate the more usual convention.)

-symbols file

-s file Read symbol table from ﬁle ﬁle.

-exec file

-e file Use ﬁle ﬁle as the executable ﬁle to e xec ute when appropriate, and for examining

pure data in conjunction with a core dump.

-se file Read symbol table from ﬁle ﬁle and use it as the executable ﬁle.

-core file

-c file Use ﬁle ﬁle as a core dump to examine.

-pid number

-p number

Connect to process ID number, as with the attach command.

-command file

-x file Execute gdb com mands from ﬁle ﬁle. See hundeﬁnedi [Command ﬁles],

page hundeﬁnedi.

-eval-command command

-ex command

Execute a single gdb command.

This option may be used multiple times to call multiple commands. It may also

be interleaved with ‘-command’ as required.

gdb -ex ’target sim’ -ex ’load’ \

-x setbreakpoints -ex ’run’ a.out

-directory directory

-d directory

Add directory to the path to search for source and script ﬁles.

Chapter 2: Getting In and Out of gdb 13

-r

-readnow Read each symbol ﬁle’s entire symbol table immediately, rather than the default,

which is to read it increm entally as it is needed. This makes startup slower,

but m akes future operations faste r.

2.1.2 Choosing Mode s

You can run gdb in various alternative modes—for example, in batch mode or quiet

mode.

-nx

-n Do not execute commands found in any initialization ﬁles. Normally, gdb exe -

cutes the commands in these ﬁles after all the command options and arguments

have been processed. See hundeﬁnedi [Command Files], page hundeﬁnedi.

-quiet

-silent

-q “Quiet”. Do not print the introductory and copyright messages. These mes-

sages are also suppressed in batch mode.

-batch Run in batch mode. Exit with status 0 after processing all the command ﬁles

speciﬁed with ‘-x’ (and all commands from initialization ﬁles, if not inhibited

with ‘-n’). Exit with nonzero status if an error occurs in executing the gdb

commands in the command ﬁles.

Batch mode may be useful for running gdb as a ﬁlter, for example to download

and run a program on another computer; in order to make this more useful, the

message

Program exited normally.

(which is ordinarily issued whenever a program running under gd b control

terminates) is not issued when running in batch mode.

-batch-silent

Run in batch mode exactly like ‘-batch’, but totally silently. All gdb output to

stdout is prevented (stderr is unaﬀected). This is much quieter than ‘-silent’

and would be useless for an interactive sess ion.

This is particularly useful when using targets that give ‘Loading section’ mes-

sages, for example.

Note that targets that give their output via gdb, as opposed to writing directly

to stdout, will also be made silent.

-return-child-result

The return code from gdb will be the return code from the child process (the

process being debugged), with the following exceptions:

• gdb exits abnormally. E.g., due to an incorrect argument or an internal

error. In this case the exit code is the same as it would have been without

‘-return-child-result’.

• The user quits with an explicit value. E.g., ‘quit 1’.

14 Debugging with gdb

• The child process never runs, or is not allowed to terminate, in which case

the exit code will be -1.

This option is useful in conjunction with ‘-batch’ or ‘-batch-silent’, when

gdb is being used as a remote program loader or simulator interface.

-nowindows

-nw “No windows”. If gdb comes with a graphical user interface (GUI) built in,

then this option tells gdb to only use the command-line interface. If no GUI is

available, this option has no eﬀect.

-windows

-w If gdb includes a GUI, then this option requires it to be used if possible.

-cd directory

Run gdb using directory as its working directory, instead of the current direc-

tory.

-fullname

-f gnu Emacs sets this option when it runs gdb as a subprocess. I t tells gdb to

output the full ﬁle name and line number in a standard, recognizable fashion

each time a stack frame is displayed (which includes each time your program

stops). This recognizable format looks like two ‘\032’ characters, followed by

the ﬁle name, line number and character position separated by colons, and a

newline. The Emacs-to-gdb interface program uses the two ‘\032’ characters

as a signal to display the source code for the frame.

-epoch The Epoch Emacs-gdb interface sets this option when it runs gdb as a subpro-

cess. It tells gdb to modify its print routines so as to allow Epoch to display

values of expressions in a separate window.

-annotate level

This option sets the annotation level inside gd b. Its eﬀect is identical to using

‘set annotate level’ (see hundeﬁnedi [Annotations], page hundeﬁnedi). The

annotation level controls how much information gdb prints together with its

prompt, values of expressions, source lines, and other types of output. Level 0

is the normal, level 1 is for use w hen gdb is run as a subprocess of gnu Emacs,

level 3 is the maximum annotation suitable for programs that control gdb, and

level 2 has been deprecated.

The annotation mechanism has largely been superseded by gdb/mi (see hun-

deﬁnedi [GDB/MI], page hundeﬁnedi).

--args Change interpretation of command line so that arguments following the exe-

cutable ﬁle are passed as command line arguments to the inferior. This option

stops option processing.

-baud bps

-b bps Set the line speed (baud rate or bits per second) of any serial interface used by

gdb for remote debugging.

-l timeout

Set the timeout (in seconds) of any communication used by gdb for remote

debugging.

Chapter 2: Getting In and Out of gdb 15

-tty device

-t device

Run using device for your program’s standard input and output.

-tui Activate the Text User Interface when starting. The Text User Interface man-

ages several text windows on the terminal, showing source, assembly, regis-

ters and gdb command outputs (see hundeﬁnedi [gdb Text User Interface],

page hundeﬁnedi). Alternatively, the Text User Interface can be enabled by

invoking the program ‘gdbtui’. Do not use this option if you run gdb from

Emacs (see hundeﬁnedi [Using gd b under gnu Emacs], page hundeﬁnedi).

-interpreter interp

Use the interpreter interp for interface with the c ontrolling program or device.

This option is meant to be set by programs which communicate with gdb using

it as a back end. See hundeﬁnedi [Command Interpreters], page hundeﬁnedi.

‘--interpreter=mi’ (or ‘--interpreter=mi2’) causes gdb to use the gdb/mi

interface (see hundeﬁnedi [The gdb/mi Interface], page hundeﬁnedi) included

since gdb version 6.0. The previous gdb/mi interface, included in gdb version

5.3 and selected with ‘--interpreter=mi1’, is deprecated. Earlier gdb/mi

interfaces are no longer supported.

-write Open the executable and core ﬁles for both reading and writing. This is equiv-

alent to the ‘set write on’ command inside gdb (see hundeﬁnedi [Patching],

page hundeﬁnedi).

-statistics

This option causes gdb to print statistics about time and memory usage after

it completes each command and returns to the prompt.

-version This option causes gdb to print its version number and no-warranty blurb, and

exit.

2.1.3 What gdb Does During Startup

Here’s the description of what gd b does during session startup:

1. Sets up the command interpreter as s peciﬁed by the command line (see hundeﬁnedi

[Mode Options], page hundeﬁnedi).

2. Reads the system-wide init ﬁle (if ‘--with-system-gdbinit’ was used when building

gdb; see hundeﬁnedi [System-wide conﬁguration and settings], page hundeﬁnedi) and

executes all the commands in that ﬁle.

3. Reads the init ﬁle (if any) in your home directory

and executes all the commands in

that ﬁle.

4. Processes command line options and operands.

5. Reads and executes the commands from init ﬁle (if any) in the current working direc-

tory. This is only done if the current directory is diﬀerent from your home directory.

Thus, you can have more than one init ﬁle, one generic in your home directory, and

On DOS/Windows systems, the home directory is the one pointed to by the HOME environment variable.

剩余492页未读，继续阅读

lwwjsdf

粉丝: 2
资源: 6

GNU调试器GDB使用手册

GDB manual.pdf

GDB Manual英文版

linux安装gdb命令,Linux gdb 命令 command not found gdb 命令详解 gdb 命令未找到 gdb 命令安装 - CommandNotFound ⚡️ 坑否...

gdb/gdb: warning: Could not load the Python gdb module from `/usr/local/share/gdb/python'.

kali gdb如何使用

openocd和gdb调试

gdb调试linux内核

python启动gdb调试

gdb 调试python代码

linux 中gdb调试

$ gdb $ gdb>

linux系统安装gdb

linux终端gdb调试

如何退出python gdb

gdal 写gdb文件

gdal保存gdb文件

gdb pi怎么退出

linux参考文献gdb

下载bochs-gdb

libpython.py import gdb ModuleNotFoundError: No module named 'gdb'

最新资源