GNU调试器gdb官方文档

需积分: 17 196 浏览量更新于2024-07-16 收藏 2.66MB PDF 举报

“Debugging with gdb（英文） - gdb调试工具官方介绍文档，版本10.0.50.20200111-git” 本文档是GNU调试器gdb的官方指南，由Richard Stallman、Roland Pesch、Stan Shebs等人撰写。gdb是一个强大的源代码级调试器，广泛应用于C、C++、Fortran等编程语言的调试工作。它允许开发者在运行程序时检查和控制程序的状态，以识别和修复错误。调试是软件开发过程中的重要环节，gdb提供了一系列功能来帮助开发者进行这一过程。以下是gdb的一些主要功能和概念： 1. **设置断点**：在程序的特定行上设置断点，使得程序在到达该点时暂停执行，方便检查此时的变量值和程序状态。 2. **单步执行**：gdb提供了`step`和`next`命令，允许开发者逐行执行程序，区别在于`step`会进入函数调用，而`next`则会跳过。 3. **查看变量**：通过`print`或`p`命令，可以查看当前作用域内变量的值，这对于理解程序执行流程非常有帮助。 4. **堆栈回溯**：使用`backtrace`或`bt`命令，可以查看调用栈，了解函数调用的顺序和上下文。 5. **修改变量**：在调试过程中，开发者可以通过`set variable`命令改变变量的值，以测试不同情况下的程序行为。 6. **运行控制**：gdb允许用户启动、停止、继续、退出程序，以及设置条件断点，只有满足特定条件时才会暂停。 7. **内存查看**：`x`命令可用于查看内存区域的内容，这对于检查内存分配和访问错误非常有用。 8. **加载和调试目标**：gdb可以调试本地或远程执行的程序，也可以调试核心转储文件，以分析程序崩溃的原因。 9. **脚本支持**：gdb支持使用GDB脚本语言，可以编写自定义命令和宏，提高调试效率。 10. **符号表处理**：gdb解析程序的符号表，能显示函数名、变量名和类型信息，使调试过程更加直观。 11. **交互式环境**：gdb提供了一个命令行界面，允许用户实时输入命令，与程序进行交互。 12. **错误报告**：如果在使用gdb时遇到问题，可以通过http://www.gnu.org/software/gdb/bugs/向开发团队提交bug和建议。 gdb作为一款强大的调试工具，能够帮助开发者深入理解程序的执行流程，定位并解决各种软件问题。掌握gdb的使用对于提升软件开发效率和质量具有重要意义。

xiv Debugging with gdb

Lseek Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 746

Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 746

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

E.14 Library List Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747

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

E.16 Memory Map Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 749

E.17 Thread List Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 750

E.18 Traceframe Info Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 750

E.19 Branch Trace Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 751

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

Appendix F The GDB Agent Expression

Mechanism . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753

F.1 General Bytecode Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753

F.2 Bytecode Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755

F.3 Using Agent Expressions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 760

F.4 Varying Target Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 761

F.5 Rationale. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 761

Appendix G Target Descriptions . . . . . . . . . . . . . 765

G.1 Retrieving Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 765

G.2 Target Description Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 765

G.2.1 Inclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 766

G.2.2 Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 766

G.2.3 OS ABI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 767

G.2.4 Compatible Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 767

G.2.5 Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 767

G.2.6 Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 767

G.2.7 Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 768

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

G.4 Enum Target Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 770

G.5 Standard Target Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 771

G.5.1 AArch64 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 771

G.5.2 ARC Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 771

G.5.3 ARM Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 772

G.5.4 i386 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 772

G.5.5 MicroBlaze Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773

G.5.6 MIPS Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773

G.5.7 M68K Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 774

G.5.8 NDS32 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 774

G.5.9 Nios II Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 774

G.5.10 Openrisc 1000 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 774

G.5.11 PowerPC Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775

G.5.12 RISC-V Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 776

G.5.13 RX Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 776

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

G.5.15 Sparc Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 777

G.5.16 TMS320C6x Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 777

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

剩余869页未读，继续阅读

修行小仙女

粉丝: 6
资源: 7

GNU调试器gdb官方文档

DebugWithGDB中文版和英文版.pdf

Debugging With GDB中文版

Debugging With GDB 无水印pdf

GDB-Debugging.zip_Debugging with GDB _Linux Debugging_gdb教程

Debugging with GDB

debugging with gdb

Debugging with gdb

debugging with GDB

大学生职业生涯规划书Word模板范文就业求职简历应聘工作PPT医疗康复专业

基于Java的学生信息管理系统的实现与操作

最新资源