東華大學圖書館 |

語系: 繁體中文

說明(常見問題)

回圖書館首頁

手機版館藏查詢

登入

回首頁

切換: 標籤 | MARC模式 | ISBD

Why programs fail = a guide to syste...

Zeller, Andreas.

FindBook

Google Book

Amazon

博客來

Why programs fail = a guide to systematic debugging /

紀錄類型:	書目-語言資料,印刷品 : Monograph/item
正題名/作者:	Why programs fail/ Andreas Zeller.
其他題名:	a guide to systematic debugging /
作者:	Zeller, Andreas.
出版者:	San Francisco, Calif. :Morgan Kaufmann ; : 2009.,
面頁冊數:	1 online resource (xxiii, 400 p.) :ill.
附註:	Description based on print version record.
內容註:	How failures come to be -- Tracking problems -- Making programs 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 -- Appendix: formal definitions.
標題:	Debugging in computer science. -
電子資源:	http://www.netlibrary.com/urlapi.asp?action=summary&v=1&bookid=249012
電子資源:	http://www.engineeringvillage.com/controller/servlet/OpenURL?genre=book&isbn=9780123745156An electronic book accessible through the World Wide Web; click for information
電子資源:	http://www.sciencedirect.com/science/book/9780123745156An electronic book accessible through the World Wide Web; click for information
ISBN:	0080923003 (electronic bk.)

Why programs fail = a guide to systematic debugging /
Zeller, Andreas.

Why programs faila guide to systematic debugging /[electronic resource] :Andreas Zeller. - 2nd ed. - San Francisco, Calif. :Morgan Kaufmann ;2009. - 1 online resource (xxiii, 400 p.) :ill.

Description based on print version record.

Includes bibliographical references and index.

How failures come to be -- Tracking problems -- Making programs 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 -- Appendix: formal definitions.

This book 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 Errors, 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. 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.

ISBN: 0080923003 (electronic bk.)Subjects--Topical Terms:

590474
Debugging in computer science.
Index Terms--Genre/Form:

542853
Electronic books.

LC Class. No.: QA76.9.D43 / Z45 2009eb

Dewey Class. No.: 005.1/4

Why programs fail = a guide to systematic debugging /
LDR:03232cam 2200337 a 45 001 893480
003 OCoLC
005 20101126
006 m d
007 cr cnu---unuuu
008 101126s2009 caua ob 001 0 eng d
020 $a 0080923003 (electronic bk.)
020 $a 9780080923000 (electronic bk.)
035 $a (OCoLC)424583972
035 $a ocn424583972
040 $a OPELS $b eng $c OPELS $d N $t $d OPELS $d OCLCQ
049 $a TEFA
050 4 $a QA76.9.D43 $b Z45 2009eb
082 0 4 $a 005.1/4 $2 22
100 1 $a Zeller, Andreas. $3 1069066
245 1 0 $a Why programs fail $h [electronic resource] : $b a guide to systematic debugging / $c Andreas Zeller.
250 $a 2nd ed.
260 $a San Francisco, Calif. : $a Oxford : $c 2009. $b Morgan Kaufmann ; $b Elsevier Science [distributor],
300 $a 1 online resource (xxiii, 400 p.) : $b ill.
500 $a Description based on print version record.
500 $a Previous ed.: Amsterdam ; London: Morgan Kaufmann, 2005.
504 $a Includes bibliographical references and index.
505 0 $a How failures come to be -- Tracking problems -- Making programs 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 -- Appendix: formal definitions.
520 $a This book 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 Errors, 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. 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.
650 0 $a Debugging in computer science. $3 590474
655 7 $a Electronic books. $2 lcsh $3 542853
856 4 0 $3 NetLibrary $u http://www.netlibrary.com/urlapi.asp?action=summary&v=1&bookid=249012
856 4 0 $3 Referex $u http://www.engineeringvillage.com/controller/servlet/OpenURL?genre=book&isbn=9780123745156 $z An electronic book accessible through the World Wide Web; click for information
856 4 0 $3 ScienceDirect $u http://www.sciencedirect.com/science/book/9780123745156 $z An electronic book accessible through the World Wide Web; click for information
994 $a C0 $b TEF