GDB权威指南：版本8.2.5的调试实战教程

需积分: 9 169 浏览量更新于2024-07-17 收藏 2.57MB PDF 举报

"GDB用户手册" GDB，全称为GNU Debugger，是GNU项目开发的一款强大的源代码级调试器，专用于在Linux、Unix等类Unix系统中进行程序调试。这本手册是权威的第十版指南，针对GDB版本8.2.50，发布日期为2019年2月1日，基于git。它由Richard Stallman、Roland Pesch、Stan Shebs等人编撰，并鼓励用户向GNU组织提交错误报告和改进意见。该手册详细介绍了如何有效地利用GDB进行调试工作。首先，章节“Debugging with gdb”是核心部分，引导读者了解GDB的基本概念和使用方法。作为一款自由软件，GDB遵循GNU Free Documentation License（FDL）版本1.3或更高版本的规定，强调了自由软件的重要性，以及免费文档对于软件自由的重要性。版权方面，自1988年至2018年，Free Software Foundation, Inc.拥有本手册的版权，用户在复制、分发和修改时需遵守FDL的条款。特别提到，购买GDB官方出版物的支持有助于基金会继续发展GNU项目，推动软件自由。手册的封面包含了几个关键信息，如“GNU Manual”，强调了它作为GNU系列的一部分，并提供了后封面的授权信息：“你可以自由复制和修改这份GNU手册。通过购买GNUPress的副本，支持我们促进GNU的开发和推广软件自由。” 接下来的内容包括详细的目录，涵盖了GDB的各个方面，如概述、基本命令、调试会话管理、数据类型查看、断点设置、步进执行、内存检查、模块加载与卸载，以及高级主题如Python脚本扩展和远程调试等。每个主题都配有详尽的示例和操作指南，确保用户能够熟练掌握和应用GDB进行高效、深入的程序调试。 GDB用户手册是一份不可或缺的资源，不仅为新手提供入门教程，也为经验丰富的开发者提供深入理解与优化程序的强大工具。无论你是软件开发者还是研究者，熟悉并掌握GDB都能极大地提升代码质量，提高问题排查效率。

xiv Debugging with gdb

Lseek Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713

Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713

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

E.14 Library List Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 714

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

E.16 Memory Map Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715

E.17 Thread List Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 716

E.18 Traceframe Info Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717

E.19 Branch Trace Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717

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

Appendix F The GDB Agent Expression

Mechanism . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721

F.1 General Bytecode Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721

F.2 Bytecode Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723

F.3 Using Agent Expressions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 728

F.4 Varying Target Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 729

F.5 Rationale. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 729

Appendix G Target Descriptions . . . . . . . . . . . . . 733

G.1 Retrieving Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733

G.2 Target Description Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733

G.2.1 Inclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734

G.2.2 Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734

G.2.3 OS ABI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735

G.2.4 Compatible Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735

G.2.5 Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735

G.2.6 Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735

G.2.7 Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736

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

G.4 Enum Target Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738

G.5 Standard Target Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 739

G.5.1 AArch64 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 739

G.5.2 ARC Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 739

G.5.3 ARM Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 740

G.5.4 i386 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 740

G.5.5 MicroBlaze Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 741

G.5.6 MIPS Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 741

G.5.7 M68K Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 742

G.5.8 NDS32 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 742

G.5.9 Nios II Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 742

G.5.10 Openrisc 1000 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 742

G.5.11 PowerPC Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 742

G.5.12 RISC-V Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744

G.5.13 S/390 and System z Features . . . . . . . . . . . . . . . . . . . . . . . . . . 744

G.5.14 Sparc Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745

G.5.15 TMS320C6x Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745

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 203. For more information, see Section 15.4.1 [C

and C++], page 203.

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

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

[Modula-2], page 213.

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

[OpenCL C], page 211.

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

剩余835页未读，继续阅读

师大一棵草

粉丝: 2
资源: 6

GDB权威指南：版本8.2.5的调试实战教程

GDB用户使用手册中文版

gdb manual

GDB使用手册（中文版）

GDB使用手册

gdb使用手册

GDB 使用手册

gdb用户手册

linux GDB 使用手册

linux GDB使用手册

gdb使用手册文档pdf

最新资源