Why Programs Fail
A Guide to Systematic Debugging
- Publisher's listprice EUR 55.95
-
23 205 Ft (22 100 Ft + 5% VAT)
The price is estimated because at the time of ordering we do not know what conversion rates will apply to HUF / product currency when the book arrives. In case HUF is weaker, the price increases slightly, in case HUF is stronger, the price goes lower slightly.
- Discount 10% (cc. 2 321 Ft off)
- Discounted price 20 885 Ft (19 890 Ft + 5% VAT)
Subcribe now and take benefit of a favourable price.
Subscribe
23 205 Ft
Availability
printed on demand
Why don't you give exact delivery time?
Delivery time is estimated on our previous experiences. We give estimations only, because we order from outside Hungary, and the delivery time mainly depends on how quickly the publisher supplies the book. Faster or slower deliveries both happen, but we do our best to supply as quickly as possible.
Product details:
- Edition number 2
- Publisher Elsevier Science
- Date of Publication 22 July 2009
- ISBN 9780123745156
- Binding Paperback
- No. of pages544 pages
- Size 234x190 mm
- Weight 710 g
- Language English 0
Categories
Long description:
Why Programs Fail: A Guide to Systematic Debugging is proof that debugging has graduated from a black art to a systematic discipline. It demystifies one of the toughest aspects of software programming, showing clearly how to discover what caused software failures, and fix them with minimal muss and fuss.
The fully updated second edition includes 100+ pages of new material, including new chapters on Verifying Code, Predicting Erors, and Preventing Errors. Cutting-edge tools such as FindBUGS and AGITAR are explained, techniques from integrated environments like Jazz.net are highlighted, and all-new demos with ESC/Java and Spec#, Eclipse and Mozilla are included.
This complete and pragmatic overview of debugging is authored by Andreas Zeller, the talented researcher who developed the GNU Data Display Debugger(DDD), a tool that over 250,000 professionals use to visualize the data structures of programs while they are running. Unlike other books on debugging, Zeller's text is product agnostic, appropriate for all programming languages and skill levels.
The book explains best practices ranging from systematically tracking error reports, to observing symptoms, reproducing errors, and correcting defects. It covers a wide range of tools and techniques from hands-on observation to fully automated diagnoses, and also explores the author's innovative techniques for isolating minimal input to reproduce an error and for tracking cause and effect through a program. It even includes instructions on how to create automated debugging tools.
The text includes exercises and extensive references for further study, and a companion website with source code for all examples and additional debugging resources is available.
MoreTable of Contents:
1. How Failures Come to Be
2. Tracking Problems
3. Making Programs Fail
4. Reproducing Problems
5. Simplifying Problems
6. Scienti?c Debugging
7. Deducing Errors
8. Observing Facts
9. Tracking Origins
10. Asserting Expectations
11. Detecting Anomalies
12. Causes and E?ects
13. Isolating Failure Causes
14. Isolating Cause-E?ect Chains
15. Fixing the Defect
Appendix: Formal De?nitions
A.1 Delta Debugging
A.2 Memory Graphs
A.3 Cause-E?ect Chains
