GDB官方手册：9.0.5版本详解——调试利器指南

需积分: 10 35 浏览量更新于2024-07-16 收藏 2.64MB PDF 举报

GDB官方手册（最新版）详细介绍了GNU源级调试器GDB，版本为9.0.50.20191111-git。该手册由Richard Stallman、Roland Pesch、Stan Shebs等人编撰，适用于那些希望深入理解并利用GDB进行程序调试的开发者。GDB作为一款强大的工具，它允许用户在程序运行时观察其内部状态，以及在发生崩溃时分析其他进程的行为。手册的核心功能被概括为四点： 1. **指定条件下的程序停止**：GDB允许用户设置断点，当满足特定条件（如特定指令执行、变量值变化等）时，程序会自动暂停执行。这对于定位代码中的错误非常关键，因为开发者可以在停止点检查变量值、调用堆栈等信息。 2. **检查程序停止时的状态**：在程序暂停后，GDB提供了丰富的调试信息，包括查看内存中的数据、调用栈跟踪、局部变量值等，帮助开发者了解程序当前的工作状态和错误可能的来源。 3. **修改程序内容并继续执行**：在分析过程中，用户可以修改变量的值，甚至改变程序的控制流，以此来模拟不同的情况，验证错误修复或测试假设。这是一种强大的调试手段，能够动态地调整程序的运行路径。 4. **启动程序并控制其行为**：GDB不仅限于单步执行，还可以在启动时传递参数或设置环境变量，从而影响程序的行为。这使得开发者能对程序的不同输入或配置进行测试，以便找出问题的普遍性。此外，手册还强调了GDB与自由软件的关系，提倡Free Software（自由软件）的理念，并鼓励读者在发现错误或改进意见时向项目提交bug报告和反馈。版权方面，此文档遵循GNU Free Documentation License Version 1.3或更高版本，允许用户在尊重协议条款下复制、分发和修改文档。通过阅读这份手册，无论是初学者还是经验丰富的开发者，都能获得关于如何高效使用GDB进行复杂程序调试的深入指导，提高开发效率和产品质量。

xiv Debugging with gdb

Lseek Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736

Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736

E.13.10 File-I/O Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736

E.14 Library List Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737

E.15 Library List Format for SVR4 Targets . . . . . . . . . . . . . . . . . . . . . . 738

E.16 Memory Map Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 739

E.17 Thread List Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 740

E.18 Traceframe Info Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 740

E.19 Branch Trace Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 741

E.20 Branch Trace Conﬁguration Format . . . . . . . . . . . . . . . . . . . . . . . . 742

Appendix F The GDB Agent Expression

Mechanism . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743

F.1 General Bytecode Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743

F.2 Bytecode Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745

F.3 Using Agent Expressions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 750

F.4 Varying Target Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 751

F.5 Rationale. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 751

Appendix G Target Descriptions . . . . . . . . . . . . . 755

G.1 Retrieving Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755

G.2 Target Description Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755

G.2.1 Inclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 756

G.2.2 Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 756

G.2.3 OS ABI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 757

G.2.4 Compatible Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 757

G.2.5 Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 757

G.2.6 Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 757

G.2.7 Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 758

G.3 Predeﬁned Target Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 759

G.4 Enum Target Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 760

G.5 Standard Target Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 761

G.5.1 AArch64 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 761

G.5.2 ARC Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 761

G.5.3 ARM Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 762

G.5.4 i386 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 762

G.5.5 MicroBlaze Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763

G.5.6 MIPS Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763

G.5.7 M68K Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 764

G.5.8 NDS32 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 764

G.5.9 Nios II Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 764

G.5.10 Openrisc 1000 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 764

G.5.11 PowerPC Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 765

G.5.12 RISC-V Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 766

G.5.13 RX Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 766

G.5.14 S/390 and System z Features . . . . . . . . . . . . . . . . . . . . . . . . . . 766

G.5.15 Sparc Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 767

G.5.16 TMS320C6x Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 767

Summary of gdb 1

Summary of gdb

The purpose of a debugger such as gdb is to allow you to see what is going on “inside”

another program while it executes—or what another program was doing at the moment it

crashed.

gdb can do four main kinds of things (plus other things in support of these) to help you

catch bugs in the act:

• Start your program, specifying anything that might aﬀect its behavior.

• Make your program stop on speciﬁed conditions.

• Examine what has happened, when your program has stopped.

• Change things in your program, so you can experiment with correcting the eﬀects of

one bug and go on to learn about another.

You can use gdb to debug programs written in C and C++. For more information, see

Section 15.4 [Supported Languages], page 213. For more information, see Section 15.4.1 [C

and C++], page 213.

Support for D is partial. For information on D, see Section 15.4.2 [D], page 219.

Support for Modula-2 is partial. For information on Modula-2, see Section 15.4.9

[Modula-2], page 223.

Support for OpenCL C is partial. For information on OpenCL C, see Section 15.4.5

[OpenCL C], page 221.

Debugging Pascal programs which use sets, subranges, ﬁle variables, or nested functions

does not currently work. gdb does not support entering expressions, printing values, or

similar features using Pascal syntax.

gdb can be used to debug programs written in Fortran, although it may be necessary

to refer to some variables with a trailing underscore.

gdb can be used to debug programs written in Objective-C, using either the Ap-

ple/NeXT or the GNU Objective-C runtime.

Free Software

gdb is free software, protected by the gnu General Public License (GPL). The GPL gives

you the freedom to copy or adapt a licensed program—but every person getting a copy also

gets with it the freedom to modify that copy (which means that they must get access to the

source code), and the freedom to distribute further copies. Typical software companies use

copyrights to limit your freedoms; the Free Software Foundation uses the GPL to preserve

these freedoms.

Fundamentally, the General Public License is a license which says that you have these

freedoms and that you cannot take these freedoms away from anyone else.

Free Software Needs Free Documentation

The biggest deﬁciency in the free software community today is not in the software—it is the

lack of good free documentation that we can include with the free software. Many of our

most important programs do not come with free reference manuals and free introductory

2 Debugging with gdb

texts. Documentation is an essential part of any software package; when an important free

software package does not come with a free manual and a free tutorial, that is a major gap.

We have many such gaps today.

Consider Perl, for instance. The tutorial manuals that people normally use are non-free.

How did this come about? Because the authors of those manuals published them with

restrictive terms—no copying, no modiﬁcation, source ﬁles not available—which exclude

them from the free software world.

That wasn’t the ﬁrst time this sort of thing happened, and it was far from the last.

Many times we have heard a GNU user eagerly describe a manual that he is writing, his

intended contribution to the community, only to learn that he had ruined everything by

signing a publication contract to make it non-free.

Free documentation, like free software, is a matter of freedom, not price. The problem

with the non-free manual is not that publishers charge a price for printed copies—that in

itself is ﬁne. (The Free Software Foundation sells printed copies of manuals, too.) The

problem is the restrictions on the use of the manual. Free manuals are available in source

code form, and give you permission to copy and modify. Non-free manuals do not allow

this.

The criteria of freedom for a free manual are roughly the same as for free software.

Redistribution (including the normal kinds of commercial redistribution) must be permitted,

so that the manual can accompany every copy of the program, both on-line and on paper.

Permission for modiﬁcation of the technical content is crucial too. When people mod-

ify the software, adding or changing features, if they are conscientious they will change

the manual too—so they can provide accurate and clear documentation for the modiﬁed

program. A manual that leaves you no choice but to write a new manual to document a

changed version of the program is not really available to our community.

Some kinds of limits on the way modiﬁcation is handled are acceptable. For example,

requirements to preserve the original author’s copyright notice, the distribution terms, or

the list of authors, are ok. It is also no problem to require modiﬁed versions to include

notice that they were modiﬁed. Even entire sections that may not be deleted or changed

are acceptable, as long as they deal with nontechnical topics (like this one). These kinds of

restrictions are acceptable because they don’t obstruct the community’s normal use of the

manual.

However, it must be possible to modify all the technical content of the manual, and then

distribute the result in all the usual media, through all the usual channels. Otherwise, the

restrictions obstruct the use of the manual, it is not free, and we need another manual to

replace it.

Please spread the word about this issue. Our community continues to lose manuals

to proprietary publishing. If we spread the word that free software needs free reference

manuals and free tutorials, perhaps the next person who wants to contribute by writing

documentation will realize, before it is too late, that only free manuals contribute to the

free software community.

If you are writing documentation, please insist on publishing it under the GNU Free

Documentation License or another free documentation license. Remember that this deci-

sion requires your approval—you don’t have to let the publisher decide. Some commercial

publishers will use a free license if you insist, but they will not propose the option; it is up

剩余859页未读，继续阅读

奥修的灵魂

粉丝: 216
资源: 10

GDB官方手册：9.0.5版本详解——调试利器指南

GDB官网用户手册（gdb.pdf）

gdb官方手册，完全指导

GDB中文手册完美版.zip

gdb官方手册中文版

gdb和gdb-server如何实现通过usb连接通信，请详细举例说明

gdb-7.2-50.el6.i686.rpm

如何编译 arm-linux-gnueabihf-gdb arm-linux-gnueabihf-gdbserver 并移植到开发板上 举例

gdb和gdb-server如何实现不适用usb转串口，直接通过type-c通信，请详细举例说明

怎么执行C:\MinGW32\bin\gdb.exe --args E:\cppcheck.exe E:\ccode\r.cpp

gdb调试risc-v程序

最新资源

如何编译 arm-linux-gnueabihf-gdb arm-linux-gnueabihf-gdbserver 并移植到开发板上举例