This specific ISBN edition is currently not available.View all copies of this ISBN edition:
While fifteen years ago, common culture had little idea of what a computer crash was, it has now become a subject of commiseration for most people in most workplaces. This book is for anybody who has to analyze and prevent Windows 2000 crashes, especially device drive authors and debuggers. It takes readers, step-by-step, through crash dump analysis and kernel debugging, including how to interpret every element of a Windows 2000 stop screen. WinDbg, configuring options, symbol paths, and DLLs are explained, as is the debugging hardware such as ports, BIOS, PCI and SCSI buses, chipsets and more. Contains some illustrations and many code samples to allow the advanced user to diagnose, and hopefully repair, the cause of the crash. Annotation c. Book News, Inc., Portland, OR (booknews.com)
"synopsis" may belong to another edition of this title.
There are two primary audiences for this material: support persons and device driver developers. Familiarity with the basic architecture of Windows 2000 is assumed. Those sections that discuss device driver debugging also assume knowledge of device drivers and the C programming language. The book is fundamentally about using the Microsoft tools to debug device drivers and perform post-mortem crash dump analysis of kernel-mode failures. Book Organization
The approach taken here will lead you on a journey from understanding basic Windows 2000 debugging concepts, through the interpretation of the stop screen, to an overview of the tools. Chapter 2 contains all of the information required to set up the debugging environment. Chapter 3 switches gears and examines the Windows 2000 stop screen. Chapter 4 wraps up the introductory material with a tour of the debuggers.
After presenting this information, we'll spend three chapters actually using these tools to do debugging and to examine hardware-specific state. Chapters 5 focuses on using the debugging tools to perform debugging tasks, and Chapter 6 follows a path that examines a target's hardware with the debugger. Chapter 7 will have us momentarily switch gears and talk about extending the debugger with our own custom extensions.
Chapter 8 discusses the interesting and little-understood topic of remote-kernel debugging-that's debugging across a modem line or a network. Chapter 9 builds on the knowledge gleaned from the first eight chapters and talks about applying the techniques to examining memory dump files (as well as everything else you could want to know about dump files and the utilities to examine them). This is followed in Chapter 10 with a discussion of other tools provided by Microsoft to aid those debugging Windows 2000 device drivers. The book is concluded with a chapter devoted to debugging resources.
The appendixes attempt to bring into one place useful information that is normally scattered between header files, knowledge base articles, and the newsgroup archives. Appendix A is a complete reference of the options and commands available in the Microsoft Kernel Debuggers. Appendix B provides a listing of the bug check codes generated by Windows 2000, along with their often-undocumented parameters, and common causes. Appendix C enumerates the NT status codes, simply because they are not referenced in any other available hard-copy documentation, and they're invaluable when reading a stop screen. A Word about Versions
Microsoft is revising the tools described in this book at an amazing clip, with each revision generally improving on the last. At the same time, prerelease builds of Windows Whistler and related versions of debugging tools are arriving almost weekly at times. Amid this flurry of activity, it is impossible to write a book on a specific version of any one tool. The approach taken here is to capture what is common and most current when discussing the tools and their various features. Except where noted, what is stated about the tools is true across versions. What are ignored are the idiosyncrasies of the specific versions of each of these tools. Once the debugging tools stabilize, as Microsoft heads from Windows 2000 into Windows Whistler and Windows NT 4.0 becomes a memory, it is hoped that this book will be revised to reflect the specifics of the shipping version of the tools and the operating system. This Book Isn't Endorsed...
Although parties within Microsoft were aware that this book was being written over the past year, it is not endorsed by Microsoft, nor was Microsoft's cooperation solicited or offered during its writing. Likewise, as I wrote the majority of this text, I was a member of the Windows NT Engineering Team at NCR Corporation and the System Software Team at Network Engines. Both NCR and Network Engines kindly encouraged and supported the effort, but no one at either company officially reviewed or endorsed this work. The contents of this book are the responsibility of the author alone. No materials that would be considered confidential or proprietary by any of these companies were used in the preparation of this work. Book's Web Site
This book has a web site at aint-it-good/kerneldebug.htm that includes a multitude of good, related information. Look there for updated pointers to information about kernel debugging and crash dump analysis for both Windows 2000 and Windows Whistler. I encourage everyone to check in there to see what's available.From the Back Cover:
The start-to-finish tutorial and reference for Windows 2000 kernel debugging!
This comprehensive guide to Windows 2000 kernel debugging will be invaluable to anyone who must analyze and prevent Windows 2000 system crashes—especially device driver authors and debuggers. Renowned kernel debugging expert Steven McDowell covers every aspect of kernel debugging and crash dump analysis—including advanced hardware debugging and other techniques barely addressed in Microsoft's documentation.
Discover what Microsoft's WinDbg debugger can (and can't) do for you, and how to configure both local and remote kernel debugging environments. Learn to use Windows 2000's crash dump feature, step by step. Learn how to start and stop errant drivers, pause target systems, retrieve system and driver state, and step through source code using breakpoints and source-level debugging.
McDowell demonstrates techniques for taking control of target systems, including finding "lost" memory blocks, setting process and thread contexts, and reviewing I/O system error logs. You'll learn how to use Microsoft's powerful Debugger Extensions to run virtually any command you choose, and master the new Driver Verifier, which can detect common mistakes in driver code with unprecedented speed and accuracy.
"About this title" may belong to another edition of this title.
Book Description Pearson Education, 2001. Condition: New. book. Seller Inventory # M0130406376
Book Description Pearson Education, 2001. Hardcover. Condition: New. Seller Inventory # DADAX0130406376
Book Description Pearson Education, 2001. Hardcover. Condition: New. Never used!. Seller Inventory # P110130406376