Dumps, Bugs and Debugging Forensics: The Adventures of Dr. Debugalov (Paperback)
暫譯: 轉儲、錯誤與除錯取證:德克·除錯洛夫博士的冒險 (平裝本)

Narasimha Vedala

  • 出版商: Opentask
  • 出版日期: 2008-11-21
  • 售價: $840
  • 貴賓價: 9.5$798
  • 語言: 英文
  • 頁數: 64
  • 裝訂: Paperback
  • ISBN: 1906717257
  • ISBN-13: 9781906717254
  • 無法訂購

買這商品的人也買了...

商品描述

Behold! Thou art holding the divine book on bugs and debugging. If you are staring at this preface in a bookshop, ask not what it is; just buy it, go home and savor each page. The explanation further might cause severe brain concussions, especially, if you are not programming savvy and never before thought that bugs don't just occur in nature but they copulate and live in computers too. I'm not talking about cockroaches nesting in your computer but about programming and hardware bugs. If you think you can withstand brain damage and not babble for the rest of your life, read on. We begin with definitions in layman terms. Dumps: when a software program or code behaves unexpectedly and dies on you, it leaves a legacy behind, a big fecal matter er...I mean...dump; crash dump. When the software application is about to die, operating system scavenges the "crap" out of it and deliver the dump to folks like us to analyze further. Debugging engineers will take this dump, load it into the analyzing tool (debugger) and sweat it out, sometimes for days and nights, to figure what went wrong in the bowels. Bugs: any kind of error or behavioral deviations of the application/program/code/phew! from actual expectations is a bug. Here is a simple experiment to find a bug: try putting finger into the live point of an electrical socket and throw the switch. If you are still alive then it is a bug; Electrical socket is not correctly wired. In the process you may actually leave a dump (definition above). See, it is all making sense now. For a layman, it can't get any clearer than what is explained here. Debugging Forensics: dump analysis techniques to find the root cause for the death of an application. This term appears in the title to catch your attention and hopefully get you to buy the book. Dr. Debugalov: the quintessential human debugger. He can merely look at the color and size of the dump and tell you the root cause. He is the inspiration for this book. Bugs are not just idle creatures to sit in the code; they are dynamic and they grow and multiply with more code and create higher dimensional bugs. They have life. This life of bugs and that of Dr. Debugalov is exploited in this book. This book brings humor to the debugging world and it is the first of its kind (if you know any other we don't believe you. We insist, this book is really the first of its kind). - "Diamonds are forever but bugs are an error." - Narasimha Vedala (circa 2008)

商品描述(中文翻譯)

看啊!你手中握著這本關於錯誤和除錯的神聖書籍。如果你在書店裡盯著這個前言,不要問這是什麼;只需買下它,回家細細品味每一頁。接下來的解釋可能會讓你的大腦受到重創,尤其是如果你對程式設計不熟悉,從未想過錯誤不僅存在於自然界中,還會在電腦中繁殖和生存。我不是在說蟑螂在你的電腦裡築巢,而是關於程式和硬體的錯誤。如果你認為自己能承受大腦損傷,並且不會在餘生中喋喋不休,那就繼續閱讀。我們將從通俗的定義開始。

轉儲(Dumps):當一個軟體程式或代碼表現出意外行為並崩潰時,它會留下遺產,一大堆糞便呃...我的意思是...轉儲;崩潰轉儲(crash dump)。當軟體應用程式即將崩潰時,作業系統會將「垃圾」清除出來,並將轉儲交給像我們這樣的人進一步分析。除錯工程師會將這個轉儲載入分析工具(除錯器)中,並努力分析,有時需要數天數夜,找出問題出在哪裡。

錯誤(Bugs):任何類型的錯誤或應用程式/程式/代碼的行為偏差,與實際預期不符的情況都是錯誤。這裡有一個簡單的實驗來找出錯誤:試著將手指放入電源插座的活端,然後打開開關。如果你還活著,那麼這就是一個錯誤;電源插座接線不正確。在這個過程中,你可能會留下轉儲(如上所定義)。看吧,這一切現在都說得通了。對於外行人來說,這裡的解釋已經無法再清楚了。

除錯法醫學(Debugging Forensics):轉儲分析技術,用於找出應用程式崩潰的根本原因。這個術語出現在書名中,以引起你的注意,希望能讓你購買這本書。德克·除錯洛夫(Dr. Debugalov):典型的人類除錯器。他僅僅通過觀察轉儲的顏色和大小,就能告訴你根本原因。他是這本書的靈感來源。錯誤不僅僅是靜止的生物,它們是動態的,隨著代碼的增長而增殖,並創造出更高維度的錯誤。它們是有生命的。這些錯誤的生命和德克·除錯洛夫的生命在這本書中得到了充分的利用。這本書為除錯世界帶來了幽默,並且是同類書籍中的第一本(如果你知道其他的,我們不相信你。我們堅持,這本書真的是同類書籍中的第一本)。

-「鑽石是永恆的,但錯誤是一種錯誤。」- Narasimha Vedala(約2008年)