Advanced windows debugging

What Hacker News says

1. rramadassJun 2026
   These sort of bugs require a lot of knowledge about a) Windows Internals b) Tools to debug at that level. Most application-level programmers won't need nor are exposed to these.

   However, if you are interested in knowing what is all involved, see; Advanced Windows Debugging by Mario Hewardt and Daniel Pravat - https://advancedwindowsdebugging.com/

   Review of the book by Raymond Chen himself! - https://devblogs.microsoft.com/oldnewthing/20071218-01/?p=24...

   Show morethread
2. JanneVeeMay 2025
   I didn't say that I was any good, just that I enjoyed it.

   I have a dog eared copy of Advanced Windows Debugging that I've used, but I've also have books around reverse engineering, disassembly and a little bit of curiosity and practice. I have also the .NET version which I haven't used as much. I also enjoyed the Vostokov books, even though there is a lack of editing in them.

   Edit to add: It is not as much focus on usage of the tool as it is about understanding what is going on in the dump file, you are ahead in knowledge if you can do stack traces and look at exception records.

   Show morethread
3. wilaSep 2023
   How about a book?

   I like "Advanced Windows Debugging" by Mario Hewardt and Daniel Pravat.

   thread
4. rramadassJul 2022
   Perhaps the book Advanced Windows Debugging by Mario Hewardt and Daniel Pravat will get you excited enough to take up "Kernel Development" work.
   thread
5. mistachkinOct 2016
   Here are a few in no particular order:

   1. Expert .NET 2.0 IL Assembler (ISBN 1590596463)

   2. Advanced Windows Debugging (ISBN 0321374460)

   3. Advanced .NET Debugging (ISBN 0321578899)

   4. .NET Framework reference source code (https://referencesource.microsoft.com/)

   5. CoreCLR source code (https://github.com/dotnet/coreclr)

   6. MSDN documentation (it's not perfect, but it's not all bad)

   Before CoreCLR was open source, I had to rely on Shared Source Common Language Infrastructure (https://en.wikipedia.org/wiki/Shared_Source_Common_Language_...).

   Show morethread
6. hitrJun 2016
   If you work with .NET ,best place to learn all common scenarios like hang,crash,high memory are Debugging Demos https://blogs.msdn.microsoft.com/tess/2008/02/04/net-debuggi...

   Many troubleshooting steps in that blog also covers DebugDiag .DebugDiag is an amazing tool which can help you collect dumps automatically for crash,high memory,IIS slow response etc.

   Another tool which can help you profile your applications easily is PerfView https://channel9.msdn.com/Series/PerfView-Tutorial .

   Perfview is built on the (Windows Event tracing) ETW infrastructure windows have .You can think of it as Lttng or perf_events linux equivalent but built into everything windows have. I think process monitor is also built on ETW. After debugging ( which is not required for lot of scenarios) the most powerfull thing in troubleshooting any issues in Windows is ETW traces IMHO.So understanding and analyzing ETW will help you troubleshoot a lot of issues.

   https://blogs.msdn.microsoft.com/ntdebugging/2009/08/27/part...

   XPERF is built to consume ETW traces https://blogs.msdn.microsoft.com/ntdebugging/tag/XPERF/ https://blogs.technet.microsoft.com/askpfeplat/2013/03/22/tr...

   Also Advanced Windows debugging[1] and Advanced .NET debugging[2] to be very good for learning debugging in windows land.

   [1] http://www.amazon.in/Advanced-Debugging-Addison-Wesley-Micro... [2]https://www.amazon.com/Advanced-NET-Debugging-Mario-Hewardt/...

   Show morethread