GDB调试指南：官方用户手册详解

需积分: 43 171 浏览量更新于2024-07-15 收藏 2.67MB PDF 举报

"GDB官网用户手册是一份详细介绍如何使用GNU Source-Level Debugger (GDB)进行软件调试的官方文档。这份手册适用于GDB版本11.0.50.20210125-git，由Richard Stallman、Roland Pesch、Stan Shebs等人编写，并由Free Software Foundation发布。手册包含了GDB在LINUX环境下的使用方法和调试技巧，是开发者进行程序调试的重要参考资源。" GDB是GNU项目的一个关键组成部分，它是一款强大的源代码级别调试器，允许程序员在运行时检查和控制程序，从而定位和修复错误。GDB支持多种编程语言，包括C、C++、Fortran、Objective-C等，可在多种操作系统上运行，包括Linux、Unix以及Windows。手册的主要内容可能涵盖以下部分： 1. **GDB基础**：这部分会介绍如何启动GDB，设置断点，单步执行，以及查看程序状态，如变量值、调用栈等。 2. **调试会话管理**：详细解释如何与GDB交互，包括命令行界面的使用，以及如何加载和调试目标程序。 3. **运行时分析**：涵盖如何在运行过程中检查内存、跟踪变量变化、查看调用堆栈，以及如何在程序出错时获取有用的错误信息。 4. **远程调试**：介绍如何通过网络对远程系统上的程序进行调试，这对于分布式开发或嵌入式系统尤其有用。 5. **脚本和自动化**：讲解如何使用GDB的脚本功能，编写自定义命令和宏，以提高调试效率。 6. **调试多线程和多进程程序**：提供关于如何处理并发执行情况的指导，如同步问题和线程间通信的调试。 7. **C++特定特性**：针对C++语言的特性，如虚函数、模板和异常处理，给出特定的调试策略。 8. **调试其他语言**：GDB支持多种语言，这部分将说明如何调试这些语言的程序，如Fortran和Objective-C。 9. **故障排查和错误报告**：如何有效地识别和解决遇到的问题，以及向GDB的bug追踪系统提交问题。 10. **高级特性和技巧**：可能包含一些高级调试技术，如使用GDB的图形前端，或者利用GDB的Python API进行扩展。通过深入学习和实践GDB用户手册，开发者可以充分利用其强大的功能，更有效地诊断和修复程序中的错误，提升软件开发的质量和效率。同时，GDB的开源性质也鼓励用户参与贡献，进一步完善其功能和文档。

xiv Debugging with gdb

Appendix F The GDB Agent

Expression Mechanism. . . . . . . . . . . . . . . . . . . . . . . . . 763

F.1 General Bytecode Design. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763

F.2 Bytecode Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 765

F.3 Using Agent Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 770

F.4 Varying Target Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 771

F.5 Rationale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 771

Appendix G Target Descriptions. . . . . . . . . . . . . . . 775

G.1 Retrieving Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775

G.2 Target Description Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775

G.2.1 Inclusion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 776

G.2.2 Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 776

G.2.3 OS ABI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 777

G.2.4 Compatible Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 777

G.2.5 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 777

G.2.6 Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 777

G.2.7 Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 778

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

G.4 Enum Target Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 780

G.5 Standard Target Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 781

G.5.1 AArch64 Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 781

G.5.2 ARC Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 781

G.5.3 ARM Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 782

G.5.4 i386 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 782

G.5.5 MicroBlaze Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783

G.5.6 MIPS Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783

G.5.7 M68K Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 784

G.5.8 NDS32 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 784

G.5.9 Nios II Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 784

G.5.10 Openrisc 1000 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 784

G.5.11 PowerPC Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 785

G.5.12 RISC-V Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 786

G.5.13 RX Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 786

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

G.5.15 Sparc Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 787

G.5.16 TMS320C6x Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 787

Appendix H Operating System Information . . 789

H.1 Process list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 789

Appendix I Trace File Format . . . . . . . . . . . . . . . . 791

Appendix J .gdb_index section format . . . . . . . . 793

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

and C++], page 217.

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

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

[Modula-2], page 228.

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

[OpenCL C], page 225.

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

剩余879页未读，继续阅读

Zhangyanfeng1

粉丝: 18
资源: 25

GDB调试指南：官方用户手册详解

掌握UNIX平台下的强大调试工具：GDB完全手册PDF

Linux下GDB调试完全手册

GDB调试工具中文使用手册详解

gdb完全手册.pdf.zip_GDB pdf_GDB中文手册_gdb_linux_linux gdb pdf

GCC中文手册.pdf GDB完全中文手册.pdf

GDB中文手册完美版.pdf

gdb调试命令手册[借鉴].pdf

GDB使用和调试手册.pdf

GDB完全中文手册.pdf

GDB调试命令手册.pdf

最新资源