How Debuggers Work: Algorithms, Data Structures, and Architecture [Paperback]

Jonathan B. Rosenberg (Author)

Book Description

Publication Date: September 27, 1996 | ISBN-10: 0471149667 | ISBN-13: 978-0471149668 | Edition: 1

A total guide to debuggers: what they do, how they work, and how to use them to produce better programs

"Debuggers are the magnifying glass, the microscope, the logic analyzer, the profiler, and the browser with which a program can be examined."-Jonathan B. Rosenberg

Debuggers are an indispensable tool in the development process. In fact, during the course of the average software project, more hours are spent debugging software than in compiling code. Yet, not many programmers really know how to constructively interpret the results they get back from debuggers. And even fewer know what makes these complex suites of algorithms and data structures tick. Now in this extremely accessible guide, Jonathan B. Rosenberg demystifies debuggers for programmers and shows them how to make better use of debuggers in their next projects.

Taking a hands-on, problem-solving approach to a complex subject, Rosenberg explains how debuggers work and why programmers use them. Most importantly, he provides practical discussions of debugger algorithms and procedures for their use, accompanied by many practical examples. The author also discusses a wide variety of systems applications, from Microsoft's Win32 debug API to a large parallel architecture.

Visit our Web site at: http://www.wiley.com/compbooks/

Editorial Reviews

From the Publisher

Debuggers are tools to help remove bugs from software. Virtually all programmers and software developers are utilizing debuggers, but few know how to interpret the results they obtain from them. Using a hands- on, problem-solving approach, this unique reference explains how debuggers work, why programmers use them, and then discusses the algorithms involved in the debugging process.

From the Back Cover

A total guide to debuggers: what they do, how they work, and how to use them to produce better programs

"Debuggers are the magnifying glass, the microscope, the logic analyzer, the profiler, and the browser with which a program can be examined."-Jonathan B. Rosenberg

Debuggers are an indispensable tool in the development process. In fact, during the course of the average software project, more hours are spent debugging software than in compiling code. Yet, not many programmers really know how to constructively interpret the results they get back from debuggers. And even fewer know what makes these complex suites of algorithms and data structures tick. Now in this extremely accessible guide, Jonathan B. Rosenberg demystifies debuggers for programmers and shows them how to make better use of debuggers in their next projects.

Taking a hands-on, problem-solving approach to a complex subject, Rosenberg explains how debuggers work and why programmers use them. Most importantly, he provides practical discussions of debugger algorithms and procedures for their use, accompanied by many practical examples. The author also discusses a wide variety of systems applications, from Microsoft's Win32 debug API to a large parallel architecture.

Visit our Web site at: http://www.wiley.com/compbooks/

See all Editorial Reviews

Product Details

• Paperback: 272 pages
• Publisher: Wiley; 1 edition (September 27, 1996)
• Language: English
• ISBN-10: 0471149667
• ISBN-13: 978-0471149668
• Product Dimensions: 9.3 x 7.5 x 0.6 inches
• Shipping Weight: 1.2 pounds (View shipping rates and policies)
• Average Customer Review: 3.3 out of 5 stars  See all reviews (11 customer reviews)
• Amazon Best Sellers Rank: #949,171 in Books (See Top 100 in Books)

Customer Reviews

Most Helpful Customer Reviews

55 of 58 people found the following review helpful:

1.0 out of 5 stars Superficial, Short: Skip it!, January 20, 2001

By 

ThomasH (Santa Clara, CA USA) - See all my reviews

This review is from: How Debuggers Work: Algorithms, Data Structures, and Architecture (Paperback)

I recall the time, as I worked on a large parallel Unix debugger, and only slowly collected facts and scraps of necessary knowledge to progress. I always wondered, why not a single book was written, which would be solely devoted to the architecture, design and implementation of symbolic debuggers?

As I saw this book announced, my expectations were high. Could this be a help in organizing my knowledge about debuggers, collected so far from semi confidential industry reports or white papers, 3-4 dissertations, several implementations, plus some 10-15 conference papers with vague descriptions of implementations, claims of spectacular achievements or with mere theoretical ideas?

No, unfortunately this is not so. This book, or rather "a booklet" is very incomplete. It literally did not told me any single detail which I would not have known already. For example, missing is the description of the very standard Unix interface to control and hold a process. Since this is not a scientific book providing more generic foundations about process tracing (such as tracking of very long time running programs, replay techniques, generating snapshots etc. etc.) than I would at least expect a solid practice orientation. This should include a complete discussion of several assemblers and typical architectures, because they provide sometimes completely different means of implementing breakpoints, watchpoints or of support for threads. In many cases a debugger must be, or can be supported by a cooperating compiler. Several interesting ideas have been implemented in the back ends, which may greatly help supporting breakpoints, finding function prologues, dealing with exceptions and asynchronous signals. I also miss the specifications and a good comparison of the two most common formats holding symbolic information, Stabs and DWARF! Etc. etc., this list of missing facts and issues could go on and on.

Usually I call a book like this one "a blah blah novel." The author claims "I know something, but I will not tell what is it." Yes, there are debuggers, yes we can program them but a lot of code is necessary to do so, yes we can stop a process and advance it instruction by instruction. Yes, yes, I know all that.

I think that will have to keep waiting for a serious book about symbolic debugging! Any takers? If I only could write well...

19 of 21 people found the following review helpful:

3.0 out of 5 stars Good if you are only interested in theory and not practice, May 5, 1998

By 

"webgeekinc" - See all my reviews

This review is from: How Debuggers Work: Algorithms, Data Structures, and Architecture (Paperback)

I have to disagree with the author. The purpose of learning about writing a debugger is to "write a debugger". Because there aren't *any* other books with practical code and examples, the author missed a golden opportunity to fill a gap.

My Win32 debugger has less than 200 lines of source code, so the assertion that debugger code is long and complex is completely false. The "concept" of debugging is a complex one, but the source code is not.

That's not to say that the book is completely useless. Some of the advice given in the book can not be found in any other resource. And without it, it probably would have taken me much longer to write my debugger. Writing a debugger is not as easy as writing any other kind of program, so the concepts covered in the book are important.

If you are interested in writing a Win32 debugger, my suggestion would be to get this book, but supplement it with an MSDN subscription (either online or on CDROM) and get the Microsoft Systems Journal CDROM with back-issues. With these three resources (and a LOT of patience) you'll be able to get your Win32 debugger up and running.

12 of 13 people found the following review helpful:

5.0 out of 5 stars A Good introductory book, May 24, 2000

By 

Hassan I Khan - See all my reviews

This review is from: How Debuggers Work: Algorithms, Data Structures, and Architecture (Paperback)

Considering there are practically *no* books around that deals with debugger theory, I would label it a pioneering effort from Mr. Rosenberg.

True that it side steps or do not discuss in detail issues which most debugger *writers* would want to know, I can understand why the author named the book 'How debuggers Work' instead of 'How to write debuggers' or 'Debugger writing: Principles and Techniques' etc. Still it gets you going and clear lots of necessary concepts.