Dumps, Bugs and Debugging Forensics: The Adventures of Dr. Debugalov (Paperback)

Narasimha Vedala

  • 出版商: Opentask
  • 出版日期: 2008-11-21
  • 售價: $810
  • 貴賓價: 9.5$770
  • 語言: 英文
  • 頁數: 64
  • 裝訂: Paperback
  • ISBN: 1906717257
  • ISBN-13: 9781906717254
  • 下單後立即進貨 (約1週~2週)

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

商品描述

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)

商品描述(中文翻譯)

瞧!你正在握著一本關於錯誤和除錯的神聖書籍。如果你正在書店裡凝視著這本前言,不要問它是什麼;只需買下它,回家細細品味每一頁。進一步的解釋可能會導致嚴重的腦震盪,特別是如果你不懂編程,從未想過錯誤不僅發生在自然界,還會在電腦中交配並生活。我不是在談論蟑螂築巢在你的電腦裡,而是指編程和硬體錯誤。如果你認為你能承受腦損傷並且不會終身嘔吐,那就繼續閱讀吧。我們從通俗的定義開始。Dump:當軟體程式或代碼表現出意外行為並且在你面前死掉時,它會留下一個遺產,一個大便物體,呃...我的意思是...傾印;崩潰傾印。當軟體應用程式即將死亡時,作業系統會將其中的「垃圾」清理出來,並將傾印交給像我們這樣的人進一步分析。除錯工程師將會將這個傾印加載到分析工具(除錯器)中,並費盡心力,有時候需要幾天幾夜,來找出問題出在哪裡。Bugs:應用程式/程式/代碼的任何錯誤或行為偏差,呼...與實際期望不符,都是一個 bug。這裡有一個簡單的實驗來找出一個 bug:試著把手指放進電源插座的活點,然後按下開關。如果你還活著,那就是一個 bug;電源插座連接錯誤。在這個過程中,你可能實際上留下了一個傾印(上面的定義)。看吧,現在一切都有意義了。對於一個門外漢來說,這裡的解釋已經再清楚不過了。除錯法醫學:傾印分析技術,用於找出應用程式死亡的根本原因。這個術語出現在標題中是為了吸引你的注意,並希望讓你買這本書。Debugalov 博士:典型的人類除錯師。他只需看看傾印的顏色和大小,就能告訴你根本原因。他是這本書的靈感來源。Bugs 不僅僅是閒置在代碼中的生物;它們是動態的,隨著更多的代碼生長和繁殖,創造出更高維度的 bugs。它們有生命。這本書利用了 bugs 的生命和 Debugalov 博士的生命。這本書為除錯世界帶來了幽默,它是第一本這樣的書(如果你知道其他的,我們不相信你。我們堅持,這本書真的是第一本這樣的書)。-「鑽石永恆,但錯誤是 bug。」- Narasimha Vedala(約2008年)