Manage Learn to apply best practices and optimize your operations.

Why Programs Fail: A Guide to Systematic Debugging -- Chapter 3, Making Programs Fail

Debugging software is a crucial and complex process. This free chapter explains how to use testing, such as functional and unit testing, in your debugging program.

Why Programs Fail As a registered member of, you're entitled to a complimentary copy of Chapter 1 of Why Programs Fail: A Guide to Systematic Debugging written by Andreas Zeller and published by Morgan Kaufman, a division of Elsevier. Chapter 3: " Making Programs Fail" explores testing for debugging, including functional and unit testing. There are detailed instructions, code examples and graphs.

Book description:

Why Programs Fail is about bugs in computer programs, how to find them, how to reproduce them, and how to fix them in such a way that they do not occur anymore. This is the first comprehensive book on systematic debugging and covers a wide range of tools and techniques ranging from hands-on observation to fully automated diagnoses, and includes instructions for building automated debuggers. This discussion is built upon a solid theory of how failures occur, rather than relying on seat-of-the-pants techniques, which are of little help with large software systems or to those learning to program. The author, Andreas Zeller, is well known in the programming community for creating the GNU Data Display Debugger (DDD), a tool that visualizes the data structures of a program while it is running.

>> Read Chapter 3: Making Programs Fail.

>> Buy the book

Printed with permission from Morgan Kaufman, a division of Elsevier. Copyright 2006. " Why Programs Fail: A Guide to Systematic Debugging" by Andreas Zeller. For more information about this book, please visit

Dig Deeper on Topics Archive