GDB 6.8.50详解：源码级调试的艺术

Debug

需积分: 5 26 浏览量更新于2024-07-31 收藏 2.1MB PDF 举报

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

30元优惠券

《使用GDB进行调试（第6.8.50版）》是一本详尽介绍GNU源级调试器GDB的权威指南。本书适合那些希望深入理解并掌握GDB调试工具的专业开发者，特别是针对GDB 6.8.50这个特定版本。作者包括Richard Stallman、Roland Pesch、Stan Shebs等人，他们鼓励读者通过发送问题和建议到http://www.gnu.org/software/gdb/bugs/与社区交流。 GDB（GNU Debugger）是一个强大的开源工具，用于在程序运行时检查和诊断代码。它支持多种编程语言，广泛应用于软件开发过程中，帮助开发者定位和修复错误，提高代码质量和效率。此书的第九版详细介绍了GDB的各项功能，包括设置断点、单步执行、查看变量值、调用栈跟踪、内存检查等核心调试技术。书中涵盖了以下几个关键知识点： 1. **GDB入门**：章节详细介绍了如何安装和启动GDB，以及基本的交互命令，如如何加载可执行文件、设置断点和启动程序。 2. **调试流程**：展示了调试工作流，包括如何使用GDB控制程序的执行，理解指令执行过程，以及如何利用调试器观察程序状态。 3. **源码级别操作**：书中深入讲解了如何在源代码级别进行调试，包括阅读和修改变量值，追踪函数调用，以及使用内建的类型系统。 4. **高级特性**：探讨了GDB的高级功能，如条件断点、动态内存管理、异常处理、性能分析等，帮助读者在复杂项目中更有效地解决问题。 5. **跨平台支持**：由于GDB是跨平台的，书中会提及不同操作系统（如Linux、Unix、Windows等）下的使用差异和兼容性。 6. **调试技巧与策略**：提供实用的调试策略和技巧，如如何高效地利用GDB的搜索功能，以及如何编写调试脚本以自动化重复任务。 7. **错误报告和社区支持**：鼓励读者参与GDB社区，提交bug报告和提出改进意见，以促进GDB的持续发展。《使用GDB进行调试（第6.8.50版）》不仅是开发者的必备参考书籍，也是对GDB深入学习者的一次全面培训。无论是初次接触GDB的新手还是经验丰富的开发者，都能从中获得宝贵的知识和实践指导，从而提升代码质量并解决复杂的编程问题。

资源详情

资源推荐

You can encourage commercial publishers to se ll more free, copylefted manuals and

tutorials by buying them, and particularly by buying c opies from the publishers that paid

for their writing or for major improvements. Meanwhile, try to avoid buying non-free

documentation at all. Check the distribution terms of a manual before you buy it, and

insist that whoever seeks your business must respect your freedom. Check the history of

the book, and try to reward the publishers that have paid or pay the authors to work on it.

The Free Software Foundation maintains a list of free documentation published by other

publishers, at http://www.fsf.org/doc/other-free-books.html.

Contributors to gdb

Richard Stallman was the original author of gdb, and of many other gnu programs. Many

others have contributed to its development. This sec tion attempts to credit major contrib-

utors. One of the virtues of free software is that everyone is free to contribute to it; with

regret, we cannot actually acknowledge everyone here. The ﬁle ‘ChangeLog’ in the gdb

distribution approximates a blow-by-blow account.

Changes much prior to version 2.0 are lost in the mists of time.

Plea: Additions to this section are particularly welcome. If you or your friends

(or enemies, to be evenhanded) have been unfairly omitted from this list, we

would like to add your names!

So that they may not regard their many labors as thankless, we particularly thank those

who shepherded gdb through major releases: Andrew Cagney (releases 6.3, 6.2, 6.1, 6.0,

5.3, 5.2, 5.1 and 5.0); Jim Blandy (release 4.18); Jason Molenda (release 4.17); Stan Shebs

(release 4.14); Fred Fish (releases 4.16, 4.15, 4.13, 4.12, 4.11, 4.10, and 4.9); Stu Grossman

and John Gilmore (releases 4.8, 4.7, 4.6, 4.5, and 4.4); John Gilmore (releases 4.3, 4.2, 4.1,

4.0, and 3.9); Jim Kingdon (releases 3.5, 3.4, and 3.3); and Randy Smith (releases 3.2, 3.1,

and 3.0).

Richard Stallman, assisted at various times by Peter TerMaat, Chris Hanson, and

Richard Mlynarik, handled releases through 2.8.

Michael Tiemann is the author of most of the gnu C++ support in gdb, with signiﬁcant

additional contributions from Per Bothner and Daniel Berlin. James Clark wrote the gnu

C++ demangler. Early work on C++ was by Peter TerMaat (who also did much general

update work leading to release 3.0).

gdb uses the BFD subroutine library to examine multiple object-ﬁle formats; BFD was

a joint project of David V. Henkel-Wallace, Rich Pixley, Steve Chamberlain, and John

Gilmore.

David Johnson wrote the original COFF support; Pace Willison did the original support

for encapsulated COFF.

Brent Benson of Harris Computer Systems contributed DWARF 2 support.

Adam de Boor and Bradley Davis contributed the ISI Optimum V support. Per Bothner,

Noboyuki Hikichi, and Aless andro Forin contributed MIPS support. Jean-Daniel Fekete

contributed Sun 386i support. Chris Hanson improved the HP9000 support. Noboyuki

Hikichi and Tomoyuki Hasei contributed Sony/News OS 3 supp ort. David Johnson con-

tributed Encore Umax support. Jyrki Kuoppala contributed Altos 3068 support. Jeﬀ

Law contributed HP PA and SOM support. Keith Packard contributed NS32K support.

4 Debugging with gdb

Doug Rabson contributed Acorn Risc Machine support. Bob Rusk contributed Harris

Nighthawk CX-UX support. Chris Smith contributed Convex support (and Fortran de-

bugging). Jonathan Stone contributed Pyramid support. Michael Tiemann contributed

SPARC support. Tim Tucker contributed support for the Gould NP1 and Gould Powern-

ode. Pace Willison contributed Intel 386 support. Jay Vosburgh contributed Symmetry

support. Marko Mlinar contributed OpenRISC 1000 support.

Andreas Schwab contributed M68K gnu/Linux support.

Rich Schaefer and Peter Schauer helped with support of SunOS shared libraries.

Jay Fenlason and Roland McGrath ensured that gdb and GAS agree about several

machine instruction sets.

Patrick Duval, Ted Goldstein, Vikram Koka and Glenn Engel helped develop remote

debugging. Intel Corporation, Wind River Systems, AMD, and ARM contributed remote

debugging modules for the i960, VxWorks, A29K UDI, and RDI targets, respectively.

Brian Fox is the author of the readline libraries providing command-line editing and

command history.

Andrew Beers of SUNY Buﬀalo wrote the language-switching code, the Modula-2 sup-

port, and contributed the Languages chapter of this manual.

Fred Fish wrote most of the support for Unix System Vr4. He also enhanced the

command-completion support to cover C++ overloaded symbols.

Hitachi America (now Renesas America), Ltd. sponsored the support for H8/300,

H8/500, and Super-H processors.

NEC sponsored the support for the v850, Vr4xxx, and Vr5xxx processors.

Mitsubishi (now Renesas) sponsored the support for D10V, D30V, and M32R/D proces-

sors.

Toshiba sponsored the support for the TX39 Mips processor.

Matsushita sponsored the support for the MN10200 and MN10300 processors.

Fujitsu sponsored the support for SPARClite and FR30 processors.

Kung Hs u, Jeﬀ Law, and Rick Sladkey added support for hardware watchpoints.

Michael Snyder added support for tracepoints.

Stu Gross man wrote gdbserver.

Jim Kingdon, Peter Schauer, Ian Taylor, and Stu Grossman made nearly innumerable

bug ﬁxes and c leanups throughout gdb.

The following people at the Hewlett-Packard Company contributed support for the PA-

RISC 2.0 architecture, HP-UX 10.20, 10.30, and 11.0 (narrow mode), HP’s implementation

of kernel threads, HP’s aC++ compiler, and the Te xt User Interface (nee Terminal User

Interface): Ben Krepp, Richard Title, John Bishop, Susan Macchia, Kathy Mann, Satish

Pai, India Paul, Steve Rehrauer, and Elena Zannoni. Kim Haase provided HP-speciﬁc

information in this manual.

DJ Delorie ported gdb to MS-DOS, for the DJGPP project. Robert Hoehne made

signiﬁcant contributions to the DJGPP port.

Cygnus Solutions has sponsored gdb maintenance and much of its development since

1991. Cygnus engineers who have worked on gdb fulltime include Mark Alexander, Jim

Blandy, Per Bothner, Kevin Buettner, Edith Epstein, Chris Faylor, Fred Fish, Martin

Hunt, Jim Ingham, John Gilmore, Stu Grossman, Kung Hsu, Jim Kingdon, John Metzler,

Fernando Nasser, Geoﬀrey Noer, Dawn Perchik, Rich Pixley, Zdenek Radouch, Keith Seitz,

Stan Shebs, David Taylor, and Elena Zannoni. In addition, Dave Brolley, Ian Carmichael,

Steve Chamberlain, Nick Clifton, JT Conklin, Stan Cox, DJ Delorie, Ulrich Drepper, Frank

Eigler, Doug Evans, Sean Fagan, David Henkel-Wallace, Richard Henderson, Jeﬀ Holcomb,

Jeﬀ Law, Jim Lemke, Tom Lord, Bob Manson, Michael Meissner, Jason Merrill, Catherine

Moore, Drew Moseley, Ken Raeburn, Gavin R omig-Koch, Rob Savoye, Jamie Smith, Mike

Stump, Ian Taylor, Angela Thomas, Michael Tiemann, Tom Tromey, Ron Unrau, Jim

Wilson, and David Zuhn have made contributions both large and small.

Andrew Cagney, Fernando Nasser, and Elena Zannoni, while working for Cygnus Solu-

tions, implemented the original gdb/mi interface.

Jim Blandy added support for preprocessor macros, while working for Red Hat.

Andrew Cagney designed gdb’s architecture vector. Many people including Andrew

Cagney, Stephane Carrez, Randolph Chung, Nick Duﬀek, Richard Henderson, Mark Ket-

tenis, Grace Sainsbury, Kei Sakamoto, Yoshinori Sato, Michael Snyder, Andreas Schwab,

Jason Thorpe, Corinna Vinschen, Ulrich Weigand, and Elena Zannoni, helped with the

migration of old architectures to this new framework.

Andrew Cagney completely re-designed and re-implemented gdb’s unwinder framework,

this consisting of a fresh new design featuring frame IDs, independent frame sniﬀers, and

the sentinel frame. Mark Kettenis implemented the dwarf 2 unwinder, Jeﬀ Johnston the

libunwind unwinder, and Andrew Cagney the dummy, sentinel, tramp, and trad unwinders.

The architecture-speciﬁc changes, e ach involving a complete rewrite of the architecture’s

frame code, were carried out by Jim Blandy, Joel Brobecker, Kevin Buettner, Andrew

Cagney, Stephane Carrez, Randolph Chung, Orjan Friberg, Richard Henderson, Daniel

Jacobowitz, Jeﬀ Johnston, Mark Kettenis, Theodore A. Roth, Kei Sakamoto, Yoshinori

Sato, Michael Snyder, Corinna Vinschen, and Ulrich Weigand.

Christian Zankel, Ross Morley, Bob Wilson, and Maxim Grigoriev from Tensilica, Inc.

contributed support for Xtensa processors. Others who have worked on the Xtensa port of

gdb in the past include Steve Tjiang, John Newlin, and Scott Foehner.

Chapter 1: A Sample gdb Session 7

1 A Sample gdb Session

You can use this manual at your leisure to read all about gdb. However, a handful of

commands are enough to get started using the debugger. This chapter illustrates those

commands.

In this sample session, we emphasize user input like this: input, to make it easier to pick

out from the surrounding output.

One of the preliminary versions of gnu m4 (a generic macro processor) exhibits the

following bug: sometimes, when we change its quote strings from the default, the commands

used to capture one macro deﬁnition within another stop working. In the following short m4

session, we deﬁne a macro foo which expands to 0000; we then use the m4 built-in defn to

deﬁne bar as the same thing. However, when we change the open quote string to <QUOTE>

and the close quote string to <UNQUOTE>, the same procedure fails to deﬁne a new synonym

baz:

$ cd gnu/m4

$ ./m4

deﬁne(foo,0000)

foo

0000

deﬁne(bar,defn(‘foo’))

bar

0000

changequote(<QUOTE>,<UNQUOTE>)

deﬁne(baz,defn(<QUOTE>foo<UNQUOTE>))

baz

Ctrl-d

m4: End of input: 0: fatal error: EOF in string

Let us use gdb to try to see what is going on.

$ gdb m4

gdb is free software and you are welcome to distribute copies

of it under certain conditions; type "show copying" to see

the conditions.

There is absolutely no warranty for gdb; type "show warranty"

for details.

(gdb)

gdb reads only enough symbol data to know where to ﬁnd the rest when needed; as a result,

the ﬁrst prompt comes up very quickly. We now tell gdb to use a narrower display width

than usual, so that examples ﬁt in this manual.

(gdb) set width 70

We need to see how the m4 built-in changequote works. Having looked at the source, we

know the relevant subroutine is m4_changequote, so we set a breakpoint there with the

gdb break command.

(gdb) break m4 changequote

Breakpoint 1 at 0x62f4: file builtin.c, line 879.

Using the run command, we start m4 running under gdb control; as long as control does

not reach the m4_changequote subroutine, the program runs as usual:

剩余448页未读，继续阅读

cainiao2

粉丝: 0
资源: 33

GDB 6.8.50详解：源码级调试的艺术

gdb-6.8a.tar.bz2

android-gdb-6.8.tar.bz2

gdb-6.8-mingw-3.tar.bz2

debugging with gdb中文版

debugging with gdb pdf 中文版

debugging with gdb: the gnu source-level 下载

debuging with gdb 中文版pdf

unity-debugging-2018.x.zip

unity-debugging-4.x.zip

unity-debugging-2019.x.zip

hwo to debug gdb

6.18-gdb,ros and roslaunch with gdb

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

debugging_with_gdb(中文版pdf)

linux参考文献gdb

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

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

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

华为debugging

最新资源