 |
GetTextbooks.co.uk
Compare Prices & Save up to 90% |
|
|
|
| Login | Sign up | My Wish List |
 | | Windows 2000 Kernel Debugging by Steven McDowell ISBN-10: 9780130406378 ISBN-10: 0-13-040637-6 ISBN-13: 9780130406378 ISBN-13: 978-0-13-040637-8 Hardcover 2001-01-05 Pearson Education Find Lowest Price |
Reviews | ||
Dont ever buy this book This book is all about how to set up the debugger and get some basic information on the error. WinDbg documentation is much much better than this. If you want some good introductory/advanced information about Kernel Debugging try getting hold of DebugFest materials from Microsoft, sells for some $200 as a kit. Thats a wonderful material on Kernel debugging. This book deservs 0 stars. Only this i cant rate as zero. Complete watse of money. | ||
Outdated, Obsolete, Full of Typographical Errors Don't even bother borrowing this book from the library. It is a waste of shelf space. My first clue should have been the book's website no longer exists. The debugging tools mentioned throughout the book have been updated (by several years) so the detailed information about their use is useless. The new versions of debugging tools come with help files that outclass this book at every turn. In fact, the book appears to be a poor interpretation of help files from previous versions of the tools. Upon close examination, the book is also full of seemingly minor errors that would cause great confusion to a reader trying to learn about debugging for the first time. I made it to Chapter 7 (skimming Chapters 5 & 6) before I decided to recycle (as in compost) my copy. | ||
Total disappointment If you are looking for some meat about debugging then this is NOT your book. IT's not beyond a debugger documentation. | ||
A waste of trees. The book is essentially useless. Claiming to address itself to administrators and developers alike, it manages to satisfy neither. The book explains on 160 (one hundred and sixty!) pages how to configure NT to produce a crash dump file; how to read a BSOD; how to run dumpexam; how to fire up a debugger; and how to get Windbag to run a debug session. Oh, I forget -- there are a few pages on the Driver verifier, too. The other 140 pages are a summary of Windbag commands (outdated) and a list of bugcheck codes and NTSTATUS values, both badly formatted, outdated versions of the corresponding header files. This reviewer had expected all of the above to take, oh, 50 pages at the outside, with the rest of the book devoted to common debugging scenarios -- why does my driver go bang with a 0x1E bugcheck? how do I find and eliminate a deadlock? what did I do wrong in my IRP canceling code? None of that is in there; and what _is_ in the book can be found in the DDK and Windbag docs, better written and more easily digested. Felix Kasza. | ||
A waste of trees. The book is essentially useless. Claiming to address itself to administrators and developers alike, it manages to satisfy neither. The book explains on 160 (one hundred and sixty!) pages how to configure NT to produce a crash dump file; how to read a BSOD; how to run dumpexam; how to fire up a debugger; and how to get Windbag to run a debug session. Oh, I forget -- there are a few pages on the Driver verifier, too. The other 140 pages are a summary of Windbag commands (outdated) and a list of bugcheck codes and NTSTATUS values, both badly formatted, outdated versions of the corresponding header files. This reviewer had expected all of the above to take, oh, 50 pages at the outside, with the rest of the book devoted to common debugging scenarios -- why does my driver go bang with a 0x1E bugcheck? how do I find and eliminate a deadlock? what did I do wrong in my IRP canceling code? None of that is in there; and what _is_ in the book can be found in the DDK and Windbag docs, better written and more asily digested. Felix Kasza. | ||