Regular marked price: $59.99Discount Price: $49.01
Cost Savings: $10.98 (18%)Price fluctuation possible.
How soon does it ship: Normal ship time within one day
Shipping? Absolutely FREE if you qualify for Super Saver Shipping.
Type of bind: Paperback
Dewey Decimal Number: 005.446
EAN num: 9780321374462
ISBN number: 0321374460
Label: Addison-Wesley Professional
Manufacturer: Addison-Wesley Professional
Quantity: 1
Page Count: 840
Printing Date: November 08, 2007
Publishing house: Addison-Wesley Professional
Sale Popularity Level: 6536
Studio: Addison-Wesley Professional
Other books you might be interested in perusing:
Editor's Notes and Comments:
Product Description:
“Who says you can’t bottle experience? Between these covers is a wealth of information: a clear, logical approach to finding and eliminating bugs. This is an absolute must-have book for anyone who develops, tests, or supports software for Microsoft Windows.”
-- Bob Wilton, Escalation Engineer, Critical Problem Resolution Team, Microsoft
“An excellent reference for both intermediate and advanced debuggers: highly practical, and filled with tricks and strategies. This book stands out from all other Win32 debugging literature, thanks to its in-depth examples—including resolving intricate problems like stack and heap corruptions.”
-- Kinshuman, Development Lead, Windows Core OS Division, Microsoft
The First In-Depth, Real-World, Insider’s Guide to Powerful Windows Debugging
For Windows developers, few tasks are more challenging than debugging—-or more crucial. Reliable and realistic information about Windows debugging has always been scarce. Now, with over 15 years of experience two of Microsoft’s system-level developers present a thorough and practical guide to Windows debugging ever written.
Mario Hewardt and Daniel Pravat cover debugging throughout the entire application lifecycle and show how to make the most of the tools currently available—-including Microsoft’s powerful native debuggers and third-party solutions.
To help you find real solutions fast, this book is organized around real-world debugging scenarios. Hewardt and Pravat use detailed code examples to illuminate the complex debugging challenges professional developers actually face. From core Windows operating system concepts to security, Windows® Vista™ and 64-bit debugging, they address emerging topics head-on—and nothing is ever oversimplified or glossed over!
This book enables you to
-
Master today’s most powerful Windows debugging tools, including NTSD, CDB, WinDbg, KD, and ADPlus
-
Debug code that wasn’t designed or written for easy debugging
-
Understand debuggers “under the hood,” and manage symbols and sources efficiently
-
Debug complex memory corruptions related to stacks and heaps
-
Resolve complex security problems
-
Debug across processes: identity tracking, RPC debugger extensions, and tracking IPCs with Ethereal
-
Find and fix resource leaks, such as memory and handle leaks.
-
Debug common thread synchronization problems
-
Learn when and how to write custom debugger extensions
-
Perform “postmortem debugging” using crash dumps and Windows Error Reporting
-
Automate debugging with DebugDiag and the Analyze Debugger command
Whether you’re a system-level or application developer, Advanced Windows Debugging delivers the deep understanding of debugging that could save you weeks on your very subsequent project.
Part I Overview
Chapter 1 Introduction to the Tools
Chapter 2 Introduction to the Debuggers
Chapter 3 Debugger Uncovered
Chapter 4 Managing Symbol and Source Files
Part II Applied Debugging
Chapter 5 Memory Corruptions Part I — Stacks
Chapter 6 Memory Corruptions Part I — Heaps
Chapter 7 Security
Chapter 8 Inter-process Communication
Chapter 9 Resource Leaks
Chapter 10 Synchronization
Part III Advanced Topics
Chapter 11 Writing Custom Debugger Extensions
Chapter 12 64-bit Debugging
Chapter 13 Postmortem Debugging
Chapter 14 Power Tools
Chapter 15 Windows Vista Fundamentals
Appendix A Application Verifier Test Settings
User popularity level:
Rated by buyers -
If you do nothing more than read the initial 4 chapters you will probably learn something. If you can get through Part II and Part III you will improve your knowledge of Windows programming and good general debugging techniques no matter how experienced you are. This is one every developer should have sitting by his PC.
Rated by buyers -
This book provides excellent coverage of the subject. I found it to be accurate and to contain the details I needed.
Rated by buyers -
I have little to add to the effusive praise of previous reviewers. This is a one-of-kind book. An instant classic.
Beware, however. As others have noted, this is definitely an _advanced_ book. If you're not comfortable with arcane command syntax, bits and bytes, and such this will be painful to incomprehensible for you. On the other hand, I dare say you will never be a true Master Debugger until you have a good grasp of this material.
You would do well to start with Debugging Microsoft .NET 2.0 Applications or the now-unavailable Debugging Applications for Microsoft .NET and Microsoft Windows. Both will give you an easier introduction to WinDbg. The latter, older volume has much more information on native code debugging than the newer version. As they also cover the Visual Studio debugger in detail, most developers need go no further than one of these.
Note that WinDbg _can_ be used with SOS and ADPlus to do some pretty fancy .NET debugging that isn't possible with Visual Studio alone. For that matter, the .NET CLR on Windows is implemented using the same Windows API as any native application. I've seen WinDbg used to trace bugs through C# application code down to find that the defect was actually in the CLR or Windows itself. John Robbins (author of the previously mentioned books) states in Chapter 6 of the latest version that "in our consulting work at Wintellect, which as you know works on the toughest bugs, we use WinDBG nearly 70 percent of the time."
Don't ignore this book just because you program in .NET!
Watch out for the font used in the listings though. Not being a master myself, I've been stumped for quite a while because the letter 'l' looks like the number '1' in the font they use. (I've been assiduously following the examples line-by-line).
I also recall being stumped because of an error or two in the text, though I admit I can't find them now. These as you can imagine could be a serious problem given the arcane and undocumented nature of quite a bit of the material. Just make sure you check the errata periodically. Ironically, the errata web page for the book is not functioning at the moment...
Rated by buyers -
This book has completely smashed every possible expectation I had when I set out to read it.
Let me put it simply. There comes a time in every software developers' life when he contemplates the age old question of, "If I were to be stranded on an island and I could bring only 3 things with me, what would they be?" Well, this would be one of the 3 items. (The other two would be Windows Internals by Russinovich and some other obvious classic like the Windows via C/C++ by Richter, or UNIX Network Programming by Stevens). This book is easily on the same playing field as such classics as those, and its only flaw is that it is not 1,000 pages because when a book like this comes along, you really just don't want it to end. There is so much useful information in here.
The chapter on LPC debugging is worth the price of the book alone, as LPC is completely undocumented and you literally will not find this type of information anywhere else. Every single chapter in this book is filled with gems, and with the plethora of average books being released recently, it really took me by surprise to read such a well thought out book that hits all the right topics in all the right ways.
That being said, it is advanced. Yes, I realize the title says it, but too many books come out with the word Advanced in the title that are merely Intermediate. You need some assembly language, you need to be comfortable with native code, you need to not be frightened at the thought of debugging something for which you have no source code. But for those that meet the pre-requisites, this is a must-have in every sense of the word for the serious developers' bookshelf.
Rated by buyers -
Chapters on debugging heap/stack corruptions are simply invaluable. Worth reading even if you think you know everything about those issues, this book will easily prove you wrong.
Find other books like this one:
