Why Programs Fail: A Guide to Systematic Debugging - Tapa blanda

Acerca del autor

Andreas Zeller is a full professor for Software Engineering at Saarland University in Saarbruecken, Germany. His research concerns the analysis of large software systems and their development process; his students are funded by companies like Google, Microsoft, or SAP. In 2010, Zeller was inducted as Fellow of the ACM for his contributions to automated debugging and mining software archives. In 2011, he received an ERC Advanced Grant, Europe's highest and most prestigious individual research grant, for work on specification mining and test case generation. His book "Why programs fail", the "standard reference on debugging", obtained the 2006 Software Development Jolt Productivity Award.

De la contraportada

Why Programs Fail, winner of the Jolt Productivity Award, has been freshly updated to bring readers up-to-speed on all the new methodologies that will help save them, their companies, and consumers a lot of headaches. Find out 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. A new edition of the first comprehensive book on systematic debugging, 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 and how to fix them, 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 fully updated second edition includes a new chapter on Learning From Mistakes how to leverage change and bug databases to learn where earlier errors were and where future ones will be. Cutting-edge approaches to reproduce crashes are explained, new insights on how to report problems are explained, and new material on tracking origins is included. All across the book, tools, references, and exercises have been updated to reflect the state of the art.

• The new edition of this award-winning productivity-booster is for any developer who has ever been frustrated by elusive bugs
• Brand new material demonstrates cutting-edge debugging techniques and tools, enabling readers to put the latest time-saving developments to work for them
• Learn by doing. New exercises and detailed examples focus on emerging tools and environments, including ReCRASH, FindBUGS, and the WHYLINE.

Supplemental material available at www.whyprogramsfail.com

Why Programs Fail, winner of the Jolt Productivity Award, has been freshly updated to bring readers up-to-speed on all the new methodologies that will help save them, their companies, and consumers a lot of headaches. Find out 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. A new edition of the first comprehensive book on systematic debugging, 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 and how to fix them, 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 fully updated second edition includes a new chapter on Learning From Mistakes how to leverage change and bug databases to learn where earlier errors were and where future ones will be. Cutting-edge approaches to reproduce crashes are explained, new insights on how to report problems are explained, and new material on tracking origins is included. All across the book, tools, references, and exercises have been updated to reflect the state of the art.

• The new edition of this award-winning productivity-booster is for any developer who has ever been frustrated by elusive bugs
• Brand new material demonstrates cutting-edge debugging techniques and tools, enabling readers to put the latest time-saving developments to work for them
• Learn by doing. New exercises and detailed examples focus on emerging tools and environments, including ReCRASH, FindBUGS, and the WHYLINE.

Supplemental material available at www.whyprogramsfail.com