|
Windows 2000 Kernel Debugging
 |
Author: Steven McDowell
List Price: $49.99
Our Price: Click to see the latest and low price
ISBN: 0130406376
Publisher: Prentice Hall PTR (05 January, 2001)
Edition: Hardcover
Sales Rank: 208,312
Average Customer Rating: 2.2 out of 5
|
Customer ReviewsRating: 1 out of 5
Total disappointment
If you are looking for some meat about debugging then this is NOT your book. IT's not beyond a debugger documentation.
Rating: 1 out of 5
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.
Rating: 3 out of 5
Good intro to the debugger, but partially out of date
This book does not teach you how to debug. It's essentially what the debugger documentation should have been 2 years ago.If you have never done any kernel debugging, this is a good starting point that will give you an overall undertanding of the process and the tools. However, now that Microsoft has rewritten all the debugger documentation, most of this information comes with the online documentation. The most unfortunate thing in my mind is that the most important chapter - remote debugging - has a major mistake in it: Figure 8-2 is wrong and will totally confuse the reader. Figure 8-2 should have the HOST machine located between the REMOTE and the TARGET machine.
Similar Products
· The Windows 2000 Device Driver Book: A Guide for Programmers (2nd Edition)
· Inside Microsoft Windows 2000, Third Edition
· Programming the Microsoft Windows Driver Model, Second Edition
|
