Why Programs Fail: A Guide to Systematic Debugging: Amazon.ca: Andreas Zeller: Books

Product Description

Review

"Andreas Zeller seeks to equip you with a comprehensive arsenal of techniques and the appropriate mind-sets for employing them." Rick Wayne, Software Development, January 2006

Book Description

The first complete guide to systematic debugging

See all Product Description

Inside This Book (Learn More)

Explore More
Concordance

Browse Sample Pages
Front Cover | Copyright | Table of Contents | Excerpt | Index

Tag this product

(What's this?)

Think of a tag as a keyword or label you consider is strongly related to this product.
Tags will help all customers organize and find favorite items.

Customer Reviews

There are no customer reviews yet on Amazon.ca

5 star:		(0)
4 star:		(0)
3 star:		(0)
2 star:		(0)
1 star:		(0)

Share your experience with this product with others

Create your own review

Most Helpful Customer Reviews on Amazon.com ^(beta)

Amazon.com: 4.6 out of 5 stars (8 customer reviews)

13 of 14 people found the following review helpful

4.0 out of 5 stars From the creator of the GNU Data Display Debugger (DDD)..., July 26 2006

By Fernando Berzal Galiano - Published on Amazon.com

This review is from: Why Programs Fail: A Guide to Systematic Debugging (Paperback)

"Why programs fail" attempts to provide a systematic approach to finding, reproducing, and fixing programming errors, with a strong focus on the automation of many debugging techniques. Zeller covers the whole debugging process:

- Problem-tracking systems are discussed, not only as tools for tracking and managing problem reports, but also as valuable idea repositories and requirements management systems.

- You will also find advice on how to set up automated tests that support debugging tasks.

- Apparently straightforward, reproducing problems can be harder that it seems, as "heisenbugs" testify (i.e. when debugging tools interfere with the problem so that it disappears when it is being observed).

- Delta debugging, an interesting application of the classical divide-and-conquer strategy, provides an automated method to simplify test cases (and focus on the truly relevant part of the problem).

- Applying the scientific method is the right way to debug (i.e. reasoning about programs to create hypotheses and performing experiments to validate or discard those hypotheses). Here, the use of a debugging logbook helps to make debugging explicit by writing down all hypotheses and observations.

- Plenty of techniques for creating hypothesis and determining the failure cause of an observed problem are covered, from static analysis tools and introducing assertions, to experimental techniques that try to make debugging more efficient.

"Why programs fail" is outstanding. Many interesting (and practical) ideas are explored. If you would like to improve your detective skills, this book is highly recommended.

8 of 8 people found the following review helpful

4.0 out of 5 stars Good material, crappy revisioning, Sep 17 2009

By HELIO PERRONI FILHO - Published on Amazon.com

This review is from: Why Programs Fail: A Guide to Systematic Debugging (Paperback)

This book is indeed a solid reference on a whole new approach to debugging, and I recommend it to every professional programmer.

I just wish they did a better revision work before publishing it, as scarcely past the third chapter you will have already ran into half a dozen bizarre errors. Misplaced or missing words are just the beginning; wait until you run into the misplaced paragraphs...

None of the errors take away this book's value, but thet are sort of a black eye in an otherwise beautiful figure.

7 of 7 people found the following review helpful

5.0 out of 5 stars Elevate your Debugging, Aug 25 2008

By Claude E. Smoot - Published on Amazon.com

This review is from: Why Programs Fail: A Guide to Systematic Debugging (Paperback)

Andreas Zeller created the GNU Data Display Debugger. That
fact set my expectations for this book. I was not
disappointed. Being a developer for over 15 years, I was
pleasantly surprised at the advances in debugging presented
in this book.

The great benefit of this book is that it uses the
scientific method to create a formal discipline for
debugging. This discipline can be automated in ways that
were unthought-of until recently. One example of this is
the DDCHANGE plug-in for Eclipse that automatically
identifies which of multiple code changes has introduced a
given bug.

I found no major faults in this book. The author's style
of writing is very enjoyable. The only thing I'd change is
to drop the second chapter as it contains material on defect
tracking that is covered elsewhere (unlike the rest of the
material where this book is pretty much the sole source of
information).

This is a fabulous book that any serious developer should
read.

› Go to Amazon.com to see all 8 reviews 4.6 out of 5 stars

Listmania!

Create a Listmania! list

Look for similar items by category

Look for similar items by subject

Feedback

Would you like to update product info or give feedback on images?

Why Programs Fail: A Guide to Systematic Debugging [Paperback]

Formats

Product Details

Product Description

Review

Book Description

Tag this product

Customer Reviews

Listmania!

Look for similar items by category

Look for similar items by subject

Feedback