Online Public Access Catalogue (OPAC)
Library,Documentation and Information Science Division

“A research journal serves that narrow

borderland which separates the known from the unknown”

-P.C.Mahalanobis


Normal view MARC view ISBD view

Why programs fail [electronic resource] : a guide to systematic debugging / Andreas Zeller.

By: Zeller, Andreas.
Material type: TextTextPublisher: Amsterdam ; Boston : Heidelberg : Elsevier/Morgan Kaufmann ; Dpunkt.verlag, c2006Description: 1 online resource (xxviii, 448 p.) : ill.ISBN: 9781558608665; 1558608664; 9780080481739 (electronic bk.); 0080481736 (electronic bk.); 3898642798 (dpunkt); 9783898642798 (dpunkt).Subject(s): Debugging in computer science | D�ebogage | COMPUTERS -- Software Development & Engineering -- Quality Assurance & TestingGenre/Form: Electronic books.Additional physical formats: Print version:: Why programs fail.DDC classification: 005.1/4 Other classification: 54.52 Online resources: EBSCOhost
Contents:
About the Author; Preface; 1 How Failures Come to Be; 2 Tracking Problems; 3 Making Programs Fail; 4 Reproducing Problems; 5 Simplifying Problems; 6 Scientific Debugging; 7 Deducing Errors; 8 Observing Facts; 9 Tracking Origins; 10 Asserting Expectations; 11 Detecting Anomalies; 12 Causes and Effects; 13 Isolating Failure Causes; 14 Isolating Cause-Effect Chains; 15 Fixing the Defect; Appendix: Formal Definitions; Glossary; Bibliography; Index.
Summary: 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. * Winner of a 2006 Jolt Productivity Award for Technical Books * Shows how to reproduce software failures faithfully, how to isolate what is important about the failure, and to discover what caused it * Describes how to fix the program in the best possible way, and shows how to create your own automated debugging tools * Includes exercises and extensive references for further study, and a companion website with source code for all examples and additional debugging resources.
Tags from this library: No tags from this library for this title. Log in to add tags.
No physical items for this record

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. * Winner of a 2006 Jolt Productivity Award for Technical Books * Shows how to reproduce software failures faithfully, how to isolate what is important about the failure, and to discover what caused it * Describes how to fix the program in the best possible way, and shows how to create your own automated debugging tools * Includes exercises and extensive references for further study, and a companion website with source code for all examples and additional debugging resources.

About the Author; Preface; 1 How Failures Come to Be; 2 Tracking Problems; 3 Making Programs Fail; 4 Reproducing Problems; 5 Simplifying Problems; 6 Scientific Debugging; 7 Deducing Errors; 8 Observing Facts; 9 Tracking Origins; 10 Asserting Expectations; 11 Detecting Anomalies; 12 Causes and Effects; 13 Isolating Failure Causes; 14 Isolating Cause-Effect Chains; 15 Fixing the Defect; Appendix: Formal Definitions; Glossary; Bibliography; Index.

Includes bibliographical references (p. 429-438) and index.

Description based on print version record.

License restrictions may limit access.

There are no comments for this item.

Log in to your account to post a comment.

Other editions of this work

Why programs fail by Zeller, Andreas. ©2006
Why programs fail by Zeller, Andreas. ©2006
Library, Documentation and Information Science Division, Indian Statistical Institute, 203 B T Road, Kolkata 700108, INDIA
Phone no. 91-33-2575 2100, Fax no. 91-33-2578 1412, ksatpathy@isical.ac.in


Visitor Counter