https://blogs.msdn.microsoft.com/debuggingtoolbox/2007/06/08/recommended-books-how-to-acquire-or-improve-debugging-skills/

This article is my answer for this comment.

First of all, this is just my opinion, not Microsoft’s opinion.

Before talking about books, let me explain something that I see over and over again.

Sometimes I’ve run across people who think they just need to know the debugger commands to become a good debugger.

This is a misconception. It’s like chess: just because you know the game rules and how to move the pieces doesn’t mean you are a good player. Actually to become good in chess you need to learn a lot more than the basics! To become great in chess you need to learn much more!

Debugging is the same. Debugging, testing and developing code are related topics. If you are a good programmer, you are a good tester and a good debugger. Of course, people that spend most of their time working with testing and creating test tools, have greater software testing skills.  People that spend most of their time debugging have greater software debugging skills.

Anyway, the three activities are totally related, so if you want to be a good debugger the first thing you should know is how to program.

For several reasons I recommend C++ then C# if you want to learn more about managed debugging.

A good debugger should know the following:

–      A programming language. C++ is recommended. Learning C++ you’ll learn C, too. Be sure to learn how to program in C++ using Object Oriented Programming. I actually learned C then C++.

–      Knowledge about Windows internals, like APIs, message flow, etc. . .

–      Ability to read disassembled code.

–      Troubleshooting tools.

–      How (and when) to use a debugger.

–      How to isolate a problem, following a scientific approach based on hypothesis.

That said, below I present a list of books that I really like the most among all the books I’ve read. They are my favorites!

It will be great to receive feedback from readers about other interesting books, so feel free to share your favorite book titles.

C/C++

Effective C++ (Meyers)

More Effective C++ (Meyers)

Efficient C++ (Bulka, Mayhew)

C++ Coding Standards ( Sutter, Alexandrescu)

Exceptional C++ and More Exceptional C++ (Herb Sutter)

C++ Common Knowledge (Stephen C. Dewhurst)

C++ Strategies and Tactics (Robert B. Murray)

Designing Object Oriented C++ Applications using the Booch Method (Martin)

Although these are my favorites you may want to check out for yourself.

C#

Programming Windows with C# (Petzold)

C# Programmer’s Cookbook (Jones)

Programming .NET Components (Lowy)

C# Cookbook (Hilyard & Teilhet)

CLR via C# 2nd Edition (Richter)

Applied Microsoft .NET Framework Programming (Jeffrey Richter)

Note: I like programming books focused on common problems or those that present short programs for a specific task. These kinds of books are more useful for my daily job than books about architecture, framework programming, etc…

Security

Writing Secure Code 2nd edition (Howard, LeBlanc)

Buffer Overflows (Foster)

Secure Coding in C and C++ (Seacord)

Rootkits (Greg Hoglund, James Butler)

Shellcoder’s Programming Uncovered (Kris Kaspersky)

Shellcoder’s Handbook (Koziol, Litchfield, Aitel, Anley, Eren, Mehta, Hassell)

Sockets, Shellcode, Porting & Coding (James C. Foster)

Exploiting Software (Greg Hoglund, Gary McGraw)

Hunting Security Bugs (Gallagher, Jeffries, Landauer)

Practical Malware Analysis (Sikorski, Honig)

Managed Code Rootkits: Hooking into Runtime Environments (Erez Metula)

I love books related to security! I’m not a security engineer, but I’m interested in knowing more about bugs and what they look like in low level terms. Moreover, these books talk about reverse engineering at some level.

 

Bugs and Software Problems

Find The Bug (Adam Barr)

It’s always important for those that want to excel at debugging to know more about bugs. It helps you to get this “sixth sense” when analyzing a source code.

 

Programming

Practical Guidelines and Best Practices for Visual Basic and Visual C# Developers (Balena, Dimauro)

.NET Gotchas (Subramaniam)

Code Complete 2nd Edition (McConnell)

Write Great Code, Volume 2 – Thinking Low-Level, Writing High Level (Hyde)

Code Craft: The Practice of Writing Excellent Code (Pete Goodliffe)

Refactoring: Improving the Design of Existing Code (Fowler, Beck, Brant, Opdyke, Roberts)

The Pragmatic Programmer: From Journeyman to Master (Andrew Hunt)

If you need to choose just one, pick up Code Complete 2nd edition.

Specifically for .NET the “Practical Guidelines…” it’s awesome.

 

Windows

 

Windows Internals (Russinovich, Salomon)

Windows NT/2000 – Native API Reference (Nebbett)

The Old New Thing (Chen)

Multithreading Applications in Win32 (Beveridge Wiener)

 

COM

ATL Internals (Rector, Sells)

Essential COM (Don Box)

Developer’s Workshop to COM and ATL 3.0 (Andrew Troelsen)

It’s very helpful to know the low level details of COM and ATL as several applications use COM at some level.

Debugging

Debugging by Thinking (Metzger)

Debugging ASP.NET (Goodyear, Peek, Fox)

The Science of Debugging (Telles, Hsieh)

Software Exorcism (Blunden)

Debugging Applications for .NET and Windows (Robbins)

Debugging .Net 2.0 Applications (Robbins)

Debugging – The 9 Indispensable Rules for Finding Even the Most Elusive Software and Hardware problems (Agans)

Debugging Windows Programs (McKay, Woodring)

Why Programs Fail: A guide to Systematic Debugging (Zeller)

Advanced Windows Debugging (Hewardt, Pravat)

Memory Dump Analysis Anthology – Volume 1 (Vostokov)

Memory Dump Analysis Anthology – Volume 2 (Vostokov)

Advanced .NET Debugging (Herwardt, Mario)

Windows Debugging Notebook – Essential User Space WinDbg Commands (Vostokov, Farah)

Inside Windows Debugging – A Practical Guide to Debugging and Tracing Strategies in Windows (Soulami, Tarik)

Some of the books above talk only about the mindset you need to be a good debugger, others are more focused on code and others talk about both.

Assembly, Disassembly and Reverse Engineering

I love this topic! If you want to be a good debugger you need to know this stuff.

Reversing – Secrets of Reverse Engineering (Eilam)

Disassembling Code (Vlad Pirogov)

Visual C++ Optimization with Assembly Code (Yury Magda)

Hacker Disassembling Uncovered  (Kaspersky)

Hacker Disassembling Uncovered 2nd Edition  (Kaspersky)

Expert .NET 2.0 IL Assembler (Lidin)

The Assembly Language Master Book (Vlad Pirogov)

The Art of Assembly Language (Hyde)

CrackProof your Software (Cerven) – old book, but still interesting.

x86 Disassembly (Wikibooks contributors)

Practical Reverse Engineering (Dang, Gazet, Bachaalany)

In my opinion Kris Kaspersky has the best disassembly books! He really knows the stuff.

If you need to choose only one book, pick up Hacker Disassembling Uncovered 2nd edition, which comes with a CD of the first book. However if you don’t want to print the content of the 1st edition from the CD, I recommend you get both books.

 

Others

The McKinsey Way (Rasiel)

The McKinsey Way is a book that had early influence on my approach to isolating problems.

debugging books的更多相关文章

  1. What are some good books/papers for learning deep learning?

    What's the most effective way to get started with deep learning?       29 Answers     Yoshua Bengio, ...

  2. How to Acquire or Improve Debugging Skills

    http://blogs.msdn.com/b/debuggingtoolbox/archive/2007/06/08/recommended-books-how-to-acquire-or-impr ...

  3. SQL Server Debugging with WinDbg – an Introduction

    Klaus Aschenbrenner Klaus Aschenbrenner provides independent SQL Server Consulting Services across E ...

  4. Debugging into .NET Core源代码的两种方式

    一.前言 .NET开源时间还不长,因为一直在做YOYOFx的关系,所似我常常有更深入的了解.NET Core和ASP.NET Core内容的需求,并且.NET Core平台与之前版本的变化太大,这也导 ...

  5. 7 Must Read Python Books

    7 Must Read Python Books I started learning Python just two years ago. Coming from a C++ and Java ba ...

  6. Configure Visual Studio 2013 for debugging .NET framework

    https://referencesource.microsoft.com/ In order to configure Visual Studio 2013 do the following in ...

  7. The Nine Indispensable Rules for HW/SW Debugging 软硬件调试之9条军规

    I read this book in the weekend, and decided to put the book on my nightstand. It's a short and funn ...

  8. [转]程序员自己写的神器 MonoDevelop 4 (Xamarin Studio) Debugging for Unity

    原文地址 http://www.cliffordroche.ca/monodevelop-4-xamarin-studio-debugging-in-unity/ MonoDevelop 4 (Xam ...

  9. 在chrome 总调试cordova出现Detached from the target. Remote debugging has been terminated with reason: Connection lost. Please re-attach to the new target

    在chrome 总调试cordova出现如下错误: "Detached from the target. Remote debugging has been terminated with ...

随机推荐

  1. LINQ基础 之 LINQ TO SQL (二)

    配置LINQ TO SQL 首先添加一个Linq to sql文件,以.dbml结尾的文件.无法把表拖拽到.dbml文件中,提示“所选对象使用不支持的数据提供程序” 解决方案 在服务器资源管理器中右键 ...

  2. About Closure

    Closure被翻译为闭包,C++11引入了Lambda表达式支持Closure,JavaScript支持Closure,Objective C支持Blocks,他们都是Closure,名字各有不同, ...

  3. <button>使用注意问题

    最近在项目的上传功能下(IE8)发现了如下的错误: 2015-08-13 09:14:03,396 WARN   [WARN] [http-8080-5] : Handler execution re ...

  4. __set()与__get() 魔术方法

    在面向对象编程的过程中,对于类当中的各个成员变量,都有不同的访问属性,比如公有的(public)属性,在类内部和类外部都可直接调用:而私有的(private)和受保护的(protected),在类外不 ...

  5. python基础之模块之os模块

    os模块 os模块的作用: os,语义为操作系统,所以肯定就是操作系统相关的功能了,可以处理文件和目录这些我们日常手动需要做的操作,就比如说:显示当前目录下所有文件/删除某个文件/获取文件大小…… 另 ...

  6. LeetCode Permutations (全排列)

    题意: 给出n个元素,请产生出所有的全排列. 思路: 注意到可能会有相同的排列出现,比如 {2,2}.还有可能是乱序列(大部分情况下都是无所谓的). 递归(1):产生的过多的多余vector. cla ...

  7. 如何用 freebayes call SNP

    1,软件介绍 FreeBayes is a Bayesian genetic variant detector designed to find small polymorphisms, specif ...

  8. Sublime Text插件:HTML+CSS+JAVASCRIPT+JSON快速格式化

    安装过程简要说明如下: 在Sublime Text中,按下Ctrl+Shift+P调出命令面板; 输入install 调出 Install Package 选项并回车; 输入pretty,并在列表中选 ...

  9. Oracle执行语句跟踪(1)——使用sql trace实现语句追踪

    系统上的某个接口提交数据经常超时(超过3秒),而我单独在后台数据库(Oracle)执行insert,只需要17ms.提交数据的客户端没有任何的调试日志,只能通过跟踪后台语句记录实际调用过程中的数据库执 ...

  10. matlab 已知函数值纵坐标值(Y值)获得对应的横坐标

    clear all;clc; x=-pi/2:pi/50:pi; y=sin(x); plot(x,y); grid on; fm=max(y) id=find(y==fm); xm=x(id) 转自 ...