Why Programs Fail: A Guide to Systematic Debugging (Record no. 49347)
[ view plain ]
| 000 -LEADER | |
|---|---|
| fixed length control field | 00962nam a2200169Ia 4500 |
| 008 - FIXED-LENGTH DATA ELEMENTS--GENERAL INFORMATION | |
| fixed length control field | 140223b2005 xxu||||| |||| 00| 0 eng d |
| 020 ## - INTERNATIONAL STANDARD BOOK NUMBER | |
| International Standard Book Number | 9781558608665 |
| Terms of availability | 0.00 |
| 082 ## - DEWEY DECIMAL CLASSIFICATION NUMBER | |
| Classification number | 005.14 |
| Item number | ZEL |
| 100 ## - MAIN ENTRY--PERSONAL NAME | |
| Personal name | Zeller, Andreas |
| 245 ## - TITLE STATEMENT | |
| Title | Why Programs Fail: A Guide to Systematic Debugging |
| 260 ## - PUBLICATION, DISTRIBUTION, ETC. (IMPRINT) | |
| Place of publication, distribution, etc. | New York |
| Name of publisher, distributor, etc. | Elsevier Science Publishing Co. |
| Date of publication, distribution, etc. | 2005 |
| 300 ## - PHYSICAL DESCRIPTION | |
| Extent | 448p |
| 500 ## - GENERAL NOTE | |
| General note | How Failures Come to Be Tracking Problems Making Problems Fail Reproducing Problems Simplifying Problems Scientific Debugging Deducing Errors Observing Facts Tracking Origins Asserting Expectations Detecting Anomalies Causes and Effects Isolating Failure Causes Isolating Cause Effect Chains Fixing the Defect Formal Definitions |
| 600 ## - SUBJECT ADDED ENTRY--PERSONAL NAME | |
| Personal name | Computer Engineering |
| 890 ## - | |
| -- | USA |
| 995 ## - RECOMMENDATION 995 [LOCAL, UNIMARC FRANCE] | |
| -- | ZEL |
| -- | 006545 |
| -- | CEE-PG0 |
| -- | 1788.22 |
| -- | 0 |
| -- | 049 |
| -- | IN493 |
| -- | 0 |
| -- | 0.00 |
| -- | 2416.52 26% |
| -- | 20071226 |
| -- | 02 |
| -- | C |
| -- | 20080208 |
| -- | Kushal Books |
| -- | Reference |
No items available.