How Should You Read This Book?

[Previous] [Next]

I divided the book into three distinct parts. You should read the first two parts (Chapters 1-7) in order because I build the information in a logical progression.

In the first part of the book, "The Gestalt of Debugging" (Chapters 1-3), I define the different types of bugs and develop a process for debugging that all great developers follow. I also discuss the infrastructure requirements necessary for proper team debugging. Finally, because you can (and should) do a tremendous amount of debugging during the coding phase, I cover how you can proactively debug as you're writing your code.

In the second part of the book, "Power Debugging" (Chapters 4-7), I explain what a debugger is and describe how various debuggers work. The more you understand your tools, the better able you are to use them. I also cover the Visual C++ and Visual Basic debuggers in considerable depth so that you can learn to maximize their usage. One thing I learned working with developers from across the industry—from the inexperienced to the very experienced—was that they were using only a tiny fraction of the power of the Visual C++ and Visual Basic debuggers. Although this sentiment might sound odd coming from an author of a book about debugging, I want to keep you out of the debugger as much as possible. As you read this book, you'll see that much of my goal for you isn't just to learn how to fix crashes but how to avoid them in the first place. But I also want to teach you to use the debuggers to their maximum effectiveness because there will be times when you're forced to use them.

In the third part of the book, "Power Tools and Techniques" (Chapters 8-15), I offer solutions to common debugging problems you'll encounter when writing Windows-based applications. I cover topics ranging from finding the source file and line number with just a crash address and how to automatically test your user interfaces to tracking down where your multithreaded program deadlocked. Most of the chapters in this section include utility programs and a tremendous amount of source code that you can learn from.

The final part of the book, "Appendixes" (Appendix A and Appendix B), provides additional information you'll find useful in your debugging adventures. In Appendix A, I explain how to read and interpret a Dr. Watson log. In Appendix B, you'll find annotated lists of resources—books, tools, and Web sites—that have helped me hone my skills as a developer/debugger.

Throughout the book, you'll notice that I've sprinkled sidebars that illustrate common debugging questions and debugging war stories. Although I enjoy answering the common debugging questions I'm asked, the real fun is in hearing about and relating the debugging war stories. I hope that by sharing with you some of the really "good" bugs I've helped solve (and some I've helped write!) you'll see the practical application of the approaches and techniques I recommend. Additionally, I want to help you avoid the mistakes that I've made.