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

需积分: 0 131 浏览量更新于2024-07-20 1 收藏 2.58MB PDF 举报

"《使用gdb进行调试》是一本详细介绍GNU源级调试器GDB的参考手册，适用于GDB 7.12.50版本，由Richard Stallman、Roland Pesch、Stan Shebs等人编著，发布日期为2017年3月24日。该书版权归Free Software Foundation所有，遵循GNU自由文档许可证（GNU FDL）版本1.3或更高版本。本书主要关注于GDB的使用技巧和深入调试方法，旨在帮助开发者理解和解决程序中的错误与问题。在《Debugging with gdb》中，作者首先对Free Software的理念进行了简要介绍，强调了开源软件的重要性以及免费软件基金会（FSF）在开发GDB和推广软件自由方面的角色。书中涵盖了GDB的基础概念，如安装、启动、基本命令以及如何设置断点、单步执行、查看变量值等核心功能。此外，还深入探讨了调试器的工作原理，包括内存管理和调试会话控制。该手册详细描述了如何通过GDB跟踪程序执行过程，定位代码中的错误，如使用watchpoints监控变量变化，分析堆栈信息，检查内存泄漏，以及利用断言和信号处理来辅助调试。书中还特别提到了如何在多线程环境中调试，这对于现代复杂应用来说尤为重要。此外，对于高级用户，章节中还包括了GDB脚本编程、Python扩展、调试器插件的使用等内容，让读者能够编写定制化的调试解决方案。书中也介绍了如何通过交互式调试器进行远程调试，这对于分布式系统和网络环境下的开发具有实际价值。最后，该书列举了对GDB做出贡献的作者和贡献者，鼓励读者积极参与社区，共同改进和完善这款强大的调试工具。《Debugging with gdb》是一本实用且详尽的指南，无论你是初次接触GDB的新手还是经验丰富的开发者，都能从中获得宝贵的知识和技能。"

xiv Debugging with gdb

Appendix F The GDB Agent Expression

Mechanism . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 689

F.1 General Bytecode Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 689

F.2 Bytecode Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 691

F.3 Using Agent Expressions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 696

F.4 Varying Target Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 697

F.5 Rationale. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 697

Appendix G Target Descriptions . . . . . . . . . . . . . 701

G.1 Retrieving Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 701

G.2 Target Description Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 701

G.2.1 Inclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 702

G.2.2 Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 702

G.2.3 OS ABI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703

G.2.4 Compatible Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703

G.2.5 Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703

G.2.6 Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703

G.2.7 Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 704

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

G.4 Enum Target Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 706

G.5 Standard Target Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 706

G.5.1 AArch64 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707

G.5.2 ARC Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707

G.5.3 ARM Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 708

G.5.4 i386 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 708

G.5.5 MicroBlaze Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 709

G.5.6 MIPS Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 709

G.5.7 M68K Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 710

G.5.8 NDS32 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 710

G.5.9 Nios II Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 710

G.5.10 PowerPC Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 710

G.5.11 S/390 and System z Features . . . . . . . . . . . . . . . . . . . . . . . . . . 711

G.5.12 Sparc Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 711

G.5.13 TMS320C6x Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 711

Appendix H Operating System Information

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713

H.1 Process list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713

Appendix I Trace File Format . . . . . . . . . . . . . . . 715

Appendix J .gdb_index section format. . . . . . . 717

Appendix K Manual pages . . . . . . . . . . . . . . . . . . . . 721

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

and C++], page 195.

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

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

[Modula-2], page 205.

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

[OpenCL C], page 203.

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

剩余797页未读，继续阅读

技术菌的blog

粉丝: 119
资源: 48

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

GDB调试指南：Debugging with gdb

GDB调试指南：最新版Debugging with GDB详解

GDB调试指南：Debugging with gdb详解

debugging with GDB

Linux下的GDB调试教程：Debugging with GDB 9th Edition

《Debugging With GDB中文版》— 掌握GDB调试技术

中式汉堡市场调研报告：2023年市场规模约为1890亿元

基于MATLAB的导航科学计算库

Docker以及Docker-Compose的安装与卸载

尚硅谷宋红康C语言精讲.zip

最新资源