How Debuggers Work: Algorithms, Data Structures, and Architecture 1st Edition

by Jonathan B. Rosenberg (Author)

11 customer reviews

ISBN-13: 978-0471149668

ISBN-10: 0471149667

Why is ISBN important?

Have one to sell? Sell on Amazon

Added to

Unable to add item to List. Please try again.

Share <Embed>

Condition: Used - Very Good

In Stock. Sold by Buy AM, Fulfilled by Amazon

Access codes and supplements are not guaranteed with used items.

26 Used from $4.99

FREE Shipping on orders over $25.

Select delivery location

Turn on 1-Click ordering

Only 2 left in stock - order soon.

Ships from and sold by Manor26.

This item does not ship to France. Please check other sellers who may ship internationally.

List Price: $54.99
Save: $16.93 (31%)

17 New from $39.58

Select delivery location

$38.06

Turn on 1-Click ordering

More Buying Choices

17 New from $39.58 26 Used from $4.99

43 used & new from $4.99

See All Buying Options

Free%20Two-Day%20Shipping%20for%20College%20Students%20with%20Amazon%20Student

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/

Customers who viewed this item also viewed

Page 1 of 1 Start overPage 1 of 1

This shopping feature will continue to load items. In order to navigate out of this carousel please use your heading shortcut key to navigate to the next or previous heading.

Ryan "elfmaster"…

8

Paperback
$44.99

Customers who bought this item also bought

Page 1 of 1 Start overPage 1 of 1

This shopping feature will continue to load items. In order to navigate out of this carousel please use your heading shortcut key to navigate to the next or previous heading.

Greg Hoglund

28

Paperback
$39.90
Brian Carrier

61

Paperback
$49.77
John R. Levine

28

Paperback
$57.07
Mr. Tony V Robinson

51

Paperback
$35.00
Michael Hale Ligh

40

Paperback
$41.95

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

See all Editorial Reviews

Product details

Paperback: 272 pages
Publisher: Wiley; 1 edition (October 11, 1996)
Language: English
ISBN-10: 0471149667
ISBN-13: 978-0471149668
Product Dimensions: 7.6 x 0.6 x 9.8 inches
Shipping Weight: 1.2 pounds (View shipping rates and policies)
Average Customer Review: 11 customer reviews
Amazon Best Sellers Rank: #2,318,080 in Books (See Top 100 in Books)
- #163 in Books > Computers & Technology > Programming > Algorithms > Data Structures
- #266 in Books > Computers & Technology > Hardware & DIY > Microprocessors & System Design > Computer Design
- #832 in Books > Computers & Technology > Programming > Software Design, Testing & Engineering > Testing

Would you like to tell us about a lower price?
If you are a seller for this product, would you like to suggest updates through seller support?

Be the first video

Your name here

Customer reviews

2 star (0%)

Write a customer review

See all 11 customer reviews

Top customer reviews

There was a problem filtering reviews right now. Please try again later.

Amazon Customer

It depends on what you're looking for...

October 18, 2010

Format: Kindle EditionVerified Purchase

If you're fairly new to software development and want a general survey of how debuggers work, and perhaps some tips on how to use them, this book may be of use to you.

I'm about to start work with a new employer on a tool chain for a new chip. I had hoped to gain some insight about debugger internals. Unfortunately, this book was not useful for me, and I actually wish I could get my money back.

Notice also that this book was published in 1996 (if I recall correctly). While much of what it covers is "timeless" (again, if you're looking for a survey book), large patches of the book are wasted on obsolete issues like debugging in Windows 95, or debugging 16-bit processes in a 32-bit Windows OS.

3 people found this helpful

Comment

October 7, 2007

Format: PaperbackVerified Purchase

This book was a disappointment. It doesn't even come close to describing modern debuggers. I'm still waiting for a good book to be published on debuggers.

Helpful

Not Helpful

Comment

ThomasH

Superficial, Short: Skip it!

January 20, 2001

Format: 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...

65 people found this helpful

Helpful

Not Helpful

Comment

J Jacob Jingleheimer Schmidt

Very superficial and fragmented

January 4, 2003

Format: Paperback

If there were any alternative books on the topic, I'd give this one 1 star, rather than 3. But for some reason there aren't any, so one has to be extra charitable. The book is EXTREMELY superficial, badly structured, fragmentary, it truly looks like a few unrelated white papers written by a younger colleague/research assistant bound together and published under the head honcho's name, a hasty, half-hearted affair.

Since this is the only thing in print covering the topic, you can't go wrong reading it, but don't expect to gain much. Perhaps working through the gdb's source code is better. Well, there's no question, of course, it's better because it's a real thing, but you might want to read this book as well, it does contain randomly located bits and pieces of relevant information.

It would be really great if this book were reworked: cleaned up, meaningfully structured, and given more depth (as well as source code.) Not sure why that's not done--such a book would definitely be commercially successful.

4 people found this helpful

Helpful

Not Helpful

Comment

Amazon Customer

Good if you are only interested in theory and not practice

May 5, 1998

Format: 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.

19 people found this helpful

Helpful

Not Helpful

Comment

Warric

We need a newer and more comprehensive debugger book

July 17, 2010

Format: Paperback

This is a good introductory book on debuggers, but for those who need the modern, deep details as well as information on pioneering into the new debugging methods of the cutting edge (reverse debugging support in gdb and Visual Studio 2010 for instance), we need a more detailed reference.

I would like to work with this author and/or anyone else who would care to contribute on developing a book to fill that need. Please feel free to contact me (my email address is public on my Amazon profile) if you'd like to collaborate or contribute or partner. I will gladly publicly acknowledge anyone who helps or gives their opinions or ideas.

- Warric

Helpful

Not Helpful

Comment