RapidJSON源码调试指南：GDB实战

4星 · 超过85%的资源需积分: 9 15 浏览量更新于2023-05-23 收藏 2.53MB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

"《Debugging with gdb》是一本由 Richard Stallman、Roland Pesch、Stan Shebs 等人编著的关于 GNU Source-Level Debugger (GDB) 的第十版教程，针对的是 GDB 8.2.50 版本，发布日期为 2018 年 7 月 8 日。这本书是 Free Software Foundation 出版的，版权属于 Free Software Foundation, Inc.，并遵循 GNU Free Documentation License 的条款。该书旨在介绍 GDB 的使用方法，帮助开发者进行深入的代码调试。在《Debugging with gdb》中，首先会有一个简短的概览，概述 GDB 在软件开发过程中的核心作用，即它作为一个强大的源代码级调试器，帮助开发者查找和修复程序中的错误。GDB 支持多种编程语言，并且对于理解复杂系统和内存管理有重要作用。章节内容涵盖了以下关键知识点： 1. **GDB 基础** - 介绍了 GDB 的安装、启动流程以及基本命令，如设置断点、查看变量值、单步执行、步进到函数等，这些都是调试程序的基础操作。 2. **源代码分析** - 教授如何通过 GDB 跟踪代码执行，理解程序内部的工作原理，包括如何检查内存、栈帧、寄存器状态，以及如何使用数据类型和指针进行深入剖析。 3. **调试技巧与策略** - 提供了高级调试技巧，如使用 watchpoints 监控特定变量的变化，使用反汇编指令探索机器代码执行，以及如何处理多线程和并发问题。 4. **调试工具链** - 讨论了如何与其他开发工具（如 Makefile、IDE 集成）协同工作，以提高调试效率。 5. **调试调试器** - 分享如何调试 GDB 本身，识别和解决可能遇到的问题，确保工具的稳定性和功能完善。 6. **贡献者与社区** - 着重介绍了 GDB 的开源特性，鼓励读者参与项目，提交 bug 报告和代码贡献，共同推动 GDB 的持续改进和发展。此外，书中还强调了 Free Software 的理念，指出使用自由软件的重要性，以及 Free Software Needs Free Documentation，强调文档对于开源项目的自由传播和维护至关重要。购买该书支持 Free Software Foundation，有助于他们继续开发和推广自由软件。《Debugging with gdb》是一本详尽的指南，无论是初次接触 GDB 还是希望提升调试技能的开发者，都能从中获得宝贵的知识和实践经验。通过这本书，读者可以深入了解如何利用 GDB 进行高效、深入的代码调试，从而提升软件质量和开发效率。

资源详情

资源推荐

xiv Debugging with gdb

Appendix F The GDB Agent Expression

Mechanism . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 709

F.1 General Bytecode Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 709

F.2 Bytecode Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 711

F.3 Using Agent Expressions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 716

F.4 Varying Target Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717

F.5 Rationale. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717

Appendix G Target Descriptions . . . . . . . . . . . . . 721

G.1 Retrieving Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721

G.2 Target Description Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721

G.2.1 Inclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 722

G.2.2 Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 722

G.2.3 OS ABI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723

G.2.4 Compatible Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723

G.2.5 Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723

G.2.6 Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723

G.2.7 Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 724

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

G.4 Enum Target Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 726

G.5 Standard Target Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 727

G.5.1 AArch64 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 727

G.5.2 ARC Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 727

G.5.3 ARM Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 728

G.5.4 i386 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 728

G.5.5 MicroBlaze Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 729

G.5.6 MIPS Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 729

G.5.7 M68K Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730

G.5.8 NDS32 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730

G.5.9 Nios II Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730

G.5.10 Openrisc 1000 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730

G.5.11 PowerPC Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730

G.5.12 S/390 and System z Features . . . . . . . . . . . . . . . . . . . . . . . . . . 731

G.5.13 Sparc Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731

G.5.14 TMS320C6x Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 732

Appendix H Operating System Information

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733

H.1 Process list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733

Appendix I Trace File Format . . . . . . . . . . . . . . . 735

Appendix J .gdb_index section format. . . . . . . 737

Appendix K Manual pages . . . . . . . . . . . . . . . . . . . . 741

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

and C++], page 199.

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

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

[Modula-2], page 209.

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

[OpenCL C], page 207.

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

剩余821页未读，继续阅读

杨领well

粉丝: 1369
资源: 20

会员权益专享

RapidJSON源码调试指南：GDB实战

DebugWithGDB中文版和英文版.pdf

debugging with gdb中文带书签特别版.pdf

Debugging With GDB中文版

debugging with gdb pdf 中文版

debugging_windbg.pdf

debugging with gdb中文版

debuging with gdb 中文版pdf

unity-debugging-2018.x.zip

unity-debugging-4.x.zip

unity-debugging-2019.x.zip

dot.net.高级调试].(advanced.dot.net.debugging).hewardt,.文字版.pdf

debugging with gdb: the gnu source-level 下载

debugging_with_gdb(中文版pdf)

Unable+to+start+debugging.+Unable+to+establish+a+connection+to+GDB.The+following+message+was+written

6.18-gdb,ros and roslaunch with gdb

hwo to debug gdb

error during job, obtaining debugging information... failed: execution error, return code 2 from org.apache.hadoop.hive.ql.exec.mr.mapredtask

Unable to start debugging. Unexpected GDB output from command "-environment-cd D:\\桌面文件\\C++". D:\\桌面文件\\C++: No such file or directory.

linux参考文献gdb

Unable to start debugging. Unexpected GDB output from command"-environment-cd D:\\Desktop\\新建文件夹".D:\\Desktop\\新建文件夹:Invalidargument.

会员权益专享

最新资源