SOFTWARE QUALITY BOOK EXCERPTS
Why Programs Fail: A Guide to Systematic Debugging -- Chapter 3, Making Programs Fail
Andreas Zeller
10.01.2007
Rating: --- (out of 5)
|
As a registered member of SearchSoftwareQuality.com, 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 www.mkp.com.
|
|
Rate this Tip
|
To rate tips, you must be a member of SearchSoftwareQuality.com.
Register now
to start rating these tips. Log in if you are already a member.
|
 |
 |
| |
RELATED CONTENT
 |
Testing and QA |
|
The Art of Debugging with GDB, DDD, and Eclipse -- Ch. 1
|
|
Managing the Test People, Chapter 6: Keeping Your Beast Effective
|
|
If I Only Changed the Software, Why is the Phone on Fire?: Embedded Debugging Methods Revealed -- Chapter 1, Debugging Other People's Code, Fast
|
|
Beautiful Code -- Chapter 7, Beautiful Tests
|
|
Practical Model-Based Testing: A Tools Approach -- Chapter 1, The Challenge
|
|
Lessons Learned in Software Testing: A Context-Driven Approach -- Chapter 3, Testing Techniques
|
|
Managing the Testing Process: Practical Tools and Techniques for Managing Hardware and Software Testing, 2nd Edition -- Chapter 2, The Test Plan
|
|
Penetration testing techniques -- Chapter 6, Professional Pen Testing for Web Applications
|
|
Software Quality Book Excerpts |
|
Perfect Software, Ch. 8: What Makes a Good Test
|
|
Seven Steps to Mastering Business Analysis, Ch. 1
|
|
Clean Code: A Handbook of Agile Software Craftsmanship, Chapter 1 -- What Is Clean Code?
|
|
The Software Project Manager's Bridge to Agility: Chapter 5, Scope Management
|
|
Software Security Engineering: A Guide for Project Managers -- Chapter 3, Requirements Engineering for Secure Software
|
|
Requirements Management Using IBM Rational RequisitePro: Chapter 1, Requirements Management
|
|
Implementing ITIL Configuration Management: Chapter 3, Determining Scope, Span and Granularity
|
|
Agile Software Development: The Cooperative Game, 2nd Edition -- Chapter 3, Communicating, Cooperating Teams
|
|
Inherent Quality Simplicity, Section V: The Evolution
|
|
Managing the Test People, Chapter 6: Keeping Your Beast Effective
|
|
DISCLAIMER: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.
|
|
|
|
|
|
|
