GDB调试指南：详解GNU源级调试器v8.3.5

需积分: 13 112 浏览量更新于2024-07-17 收藏 2.58MB PDF 举报

GDB调试参考手册是一份详尽的文档，专门介绍GNU源级调试器GDB（The GNU Source-Level Debugger）。本手册针对的是GDB的第10版，版本号为8.3.50，发布日期为2019年3月16日，基于Git。作者包括Richard Stallman、Roland Pesch和Stan Shebs等人，他们鼓励读者在遇到问题时通过邮件地址http://www.gnu.org/software/gdb/bugs/ 报告bug或提出建议。手册的主题围绕GDB的核心功能，即在Linux等自由软件环境下进行源代码级别的程序调试。它不仅提供了深入的技术指导，还强调了GDB在支持自由软件开发中的重要性，这与Free Software（自由软件）和Free Software Needs Free Documentation的理念相一致。版权方面，该手册遵循GNU Free Documentation License，版本1.3或更高，允许用户在特定条件下复制、分发和修改文档。内容概览包括： 1. **简介**：首先对GDB进行了简短的总结，让读者了解其在软件开发过程中的基本作用。 2. **Free Software**：阐述了自由软件的概念，强调了GDB作为自由软件项目的重要性，以及它如何促进开源社区的发展。 3. **Free Software Needs Free Documentation**：指出高质量的文档对于自由软件的支持至关重要，免费且可修改的文档是推动技术传播的关键。 4. **作者贡献**：列出了主要的开发者名单，体现了GDB作为一个开放源码项目的协作精神。此外，手册还包含了详细的目录，涵盖了诸如设置、命令行交互、调试技巧、断点、内存操作、异常处理等各种主题，适合不同层次的开发者，从初学者到高级用户都能从中获益。通过阅读这份手册，读者可以学习如何有效地利用GDB来诊断和修复程序中的错误，提升编程技能和软件质量。对于任何需要在Linux环境中进行软件调试的开发人员来说，这份GDB调试参考手册都是不可或缺的资源。

xiv Debugging with gdb

Lseek Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715

Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715

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

E.14 Library List Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 716

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

E.16 Memory Map Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717

E.17 Thread List Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 718

E.18 Traceframe Info Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 719

E.19 Branch Trace Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 719

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

Appendix F The GDB Agent Expression

Mechanism . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723

F.1 General Bytecode Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723

F.2 Bytecode Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725

F.3 Using Agent Expressions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730

F.4 Varying Target Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731

F.5 Rationale. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731

Appendix G Target Descriptions . . . . . . . . . . . . . 735

G.1 Retrieving Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735

G.2 Target Description Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735

G.2.1 Inclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736

G.2.2 Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736

G.2.3 OS ABI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737

G.2.4 Compatible Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737

G.2.5 Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737

G.2.6 Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737

G.2.7 Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738

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

G.4 Enum Target Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 740

G.5 Standard Target Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 741

G.5.1 AArch64 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 741

G.5.2 ARC Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 741

G.5.3 ARM Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 742

G.5.4 i386 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 742

G.5.5 MicroBlaze Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743

G.5.6 MIPS Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743

G.5.7 M68K Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744

G.5.8 NDS32 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744

G.5.9 Nios II Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744

G.5.10 Openrisc 1000 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744

G.5.11 PowerPC Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744

G.5.12 RISC-V Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 746

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

G.5.14 Sparc Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747

G.5.15 TMS320C6x Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747

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

剩余837页未读，继续阅读

Bruceoxl

粉丝: 5w+
资源: 45

GDB调试指南：详解GNU源级调试器v8.3.5

gdb调试手册（pdf文档）

gdb中文调试手册

gdb调试器使用手册

gdb调试 pwn

gdb调试命令行怎么删除

linux参考文献gdb

cubeIDE gdb调试

gdb pocket reference下载

linux系统怎么打断点

gdb 异常如何打印cause

最新资源