|
Login to ask the library to add a book.
|
|
Active Filter Settings
No Active Filters
|
|
|
|
|
first record
| previous record
| next record
| last record
|
full | marc
|
Record 1 of 1
|
|
| |
Total Requests 0 Unsatisfied Requests 0
|
|
You searched IISERK - Title: [Widescreen].
|
| Request |
|
|
Call Number
|
005.1/4
|
|
Author
|
Zeller, Andreas.
|
|
Title
|
Why programs fail [electronic resource] : a guide to systematic debugging / Andreas Zeller.
|
|
Publication
|
Amsterdam ; Boston : Elsevier/Morgan Kaufmann ; Heidelberg : dpunkt.verlag, c2006.
|
|
Material Info.
|
xxviii, 448 p. : ill. ; 24 cm.
|
|
Summary Note
|
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.
|
|
Notes
|
Includes bibliographical references (p. 429-438) and index.
|
|
Notes
|
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.
|
|
Notes
|
Electronic reproduction. Amsterdam : Elsevier Science & Technology, 2007.
|
|
ISBN
|
9781558608665
|
|
ISBN
|
1558608664
|
|
Subject
|
Debugging in computer science.
|
|
Subject
|
DeĢbogage.
|
|
Subject
|
Electronic books.
|
|
Added Entry
|
ScienceDirect (Online service)
|
|
Date
|
Year, Month, Day:01405141
|
|
Link
|
An electronic book accessible through the World Wide Web; click for information ScienceDirect
|
|
|
|
|
