调试九法（Debugging of nine）.docVIP

调试九法（Debugging of nine） There was a period of time in which I studied the debugging method and systematically read some books. Among them, there was a book comparison recommendation, which was debugging nine methods: the wrong way of troubleshooting. The book itself is very thin, will soon be able to read, but the content is very practical, I later in the board, if have no idea, according to the principle of debugging turn over, basically can solve the problem. Heres a list of amazons introduction to the book: Nine the debugging method: the way of software and hardware error trying to mainly introduces the debugging of nine golden rule, and combined with the actual environment tells the story of how to use them properly. The debugging method of nine: software and hardware error way of screening, the content is not on any platform, any language or any tool that tells the key is to find the cause of the error, and fix them to efficiently track and solve the problem of software and hardware. The debugging method of nine: software and hardware error way of screening, suitable for all hardware and software from personnel of course of reading. The following is an excerpt from the book, which is helpful for debugging software and hardware. Rule 1: understand the system Read the manual: there are ways to use the system correctly. Read each detail carefully: the problem may be in the chapter youre not interested in, and dont be afraid of the thickness of the manual. Basic knowledge: knowing what is normal to know what is wrong. Understanding workflow: helps locate bugs. Understand tools: what the debugging tools can do and what you cant do. Go through the details: read the manual instead of guessing or recalling the contents of the manual. Rule 2: manufacturing failure Manufacturing failure: the purpose is to observe it, find the cause, and check if it has been fixed. Start from scratch: a bug may be caused by a series of operations or operations, and a return to the initial