Inside Windows Debugging: A Practical Guide to Debugging and Tracing Strategies in Windows® [Formato Kindle]

Inside Windows Debugging is the latest book on in-depth debugging and tracing strategies written by an author with an inside look into core techniques of Windows; some of which he worked on directly.

With all the latest programming languages and integrated development environments aimed at making writing software applications more accessible, creating applications has never been easier than today. Unfortunately, creating an application is only one part of the equation, getting it to work correctly is the other - usually much harder - part. This book focuses on exactly that harder part; identifying, tracing and resolving bugs in your application as well as preventing them in the first place.

Many still think of debugging as an activity after a software application has been finished and users start to experience issues that require investigation. This, however, is far from the truth these days since many development idioms such as test-driven development (TDD) actually promote debugging during development phases.

The book is divided into three parts, the first providing a bit of background about the evolution and architecture of Windows, the Windows Developer Interface as well as the Microsoft Developer Tools. The second part introduces the basics of debugging, how the Windows debuggers actually work and debugging your application after a crash (postmortem) before moving to more advanced techniques such as scripting the debugger, debugging the WOW64 environment, code analysis tools, debugging system internals as well as looking at common debugging scenarios. The third part introduces strategies to trace and analyze application behavior using different mechanism and tools such as the Event Tracing for Windows (ETW) and the accompanying Windows Performance Analysis Tool (Xperf). Finally, two appendices provide a quick start on how to use the WinDbg debugger to accomplish both user-mode and kernel-mode debugging tasks.

This book is not aimed at the novice developer by any means since a general understanding of C++ and/or C# as well as the Win32 platform and/or the .NET framework is required. The author does provide an excellent job by introducing basic concepts prior to moving to more advanced topics so that nobody really should get lost while moving from chapter to chapter. By not just preaching the theories but also presenting real-world debugging scenarios, the author also manages to provide developers with methods and tools they immediately can use in their daily routine.

I have always been a fan of most books coming from Microsoft Press and this one is no exception: a wealth of information using an inside look into the underlying mechanics and paired with an engaging writing style makes for another book every serious developer should have on his/her shelf.

Since most of the core/kernel elements of Windows haven't changed since NT in the late 80's, most of the "new" stuff is in the form of API's. Soulami assumes a basic working knowledge of C/C++ or C#, but doesn't start at such a high level that you get lost in either the debugger or the tracer. This book is REALLY up to date on windows, and will catch you up even if you are still working on an NT base.

Chapters include: 1. How to develop software for Windows 2. Getting started (debugging for fun and profit section) 3. How debuggers work (pretty basic but very complete, covers both User and Kernel modes) 4. Postmortem Debugging (JIT vs. dump techniques. Goes much deeper than the day to day systems engineer will usually go) 5. Beyond the Basics (the real meat of the book-- awesome-- data vs. code breakpoints, scripts, etc.) 6. Code analysis tools (fair to C/++ and sharp, with many actual/not just pseudo/ code examples that are well thought out and RUN); 7. Expert Debugging Tricks (we finally get to the fun and profit piece-- many techniques that are effective but unusual, and probably wouldn't be attempted by the usual coder without this book's help on avoiding potholes); 8 and 9 are a whole collection of very cool "scenarios" covering all the NIGHTMARES created by threads and multiprocessors such as race conditions, deadlocks, stack/heap and access problems, etc. These two chapters are worth the price of the whole book; 10 gets into the console subsystem and concludes this section.

Section two (about 120 pages) switches themes with three chapters about Xperf. In short, if you try to run traces as you develop your software using just ETW (event tracing for Windows), you'll soon get overwhelmed and give it up. This means you're losing one of the best "secret sauces" of the Windows 7 SDK (a way to integrate what's already been perfected, instead of reinventing every wheel, with proven code connected with an already debugged ETW web). The way to tap into that secret sauce IS Xperf.

The two excellent appendices give user and kernel debug quick start examples that make this book as much as a reference and tutorial as a step by step learning guide.

Beyond debugging, there is a LOT of information on how to develop superior software USING the debugger, not for debugging, but for software analysis, code vs. operating system, security, and development cycle issues like static vs. runtime analysis. Any good or prospective windows developer will benefit from this wealth of info. This is over 500 pages PACKED with wisdom and experience, well worth the price as a career enhancer or builder.

This book is awesome. It will become your bible for windows debugging, and covers both theoretical aspects such as how the kernel & userland fit together in Windows, details on how 64 bit & 32 bit cohabit etc, and real-world expertise on debugging strategies for remote, local, and virtual machine scenarios. If you are programming or supporting Windows apps & servers, then you want this book. For novices, if you've not debugged an NT BSOD yet then this will give you enough understanding and straightforward tips to do so yourself, and for experts, if you don't learn something new from this book I'd be very surprised. The kindle edition is easy to read most of the time (on my large-screen DX), and at 500+ pages there's a lot of great material to work through. I'll say it again: Awesome.