I am fairly familiar with WinDbg and didn't know about OllyDbg before. From the statistics in this forum, it seems that OllyDbg is twice as popular as WinDbg. Sometimes WinDbg can be frustrating, so I wonder whether I should switch.

To make this question less opinion based, these are my requirements:

  • be able to debug .NET. From my research it seems that OllyDbg might not be as good as WinDbg with SOS and SOSEX
  • do scripting. Here it seems OllyDbg is better. There are many scripts archived in a single place, which is not the case for WinDbg.
  • analyze mini dump files. This could be a blocker: while the OllyDbg website states something about post mortem dump, I was unable to find an option to open a dump immediately (File/Open).
  • record logs of what I'm doing to be able to give it to the customer. From the Google picture search I only see screenshots from registers, memory etc. I have not seen something similar to the WinDbg command output window.

Given these core requirements, should I give OllyDbg a try?

Version information: OllyDbg 2.01

  • 2
    Although this question has already been answered, I believe it's worth mentioning that WinDBG has a python extension called PyKD which might make it easier to automate the desired task -- assuming your problem is also with the scripting interface. It won't solve the existing problem of the availability of scripts, which are more easily available - and in greater quantity - for OdbgScript but that shouldn't keep you away from WinDBG. As already said by Mr. Geffner, it's not enough of a reason to make the change.
    – TDKPS
    Commented Jan 10, 2014 at 13:28
  • It's true, some tasks can just not be automated good enough, so I'm always looking for extensions or write extensions on my own. Thanks for the suggestion. I downloaded and installed PyKD. Looks promising. I guess Stackoverflow is the place to ask questions about PyKD if I'm in trouble. Commented Jan 10, 2014 at 20:12
  • Third potential: IDA's debugger. Both 32-bit and 64-bit debugging, cross platform, has internal and Python scripting support, and probably does .NET too (I didn't check), and a bunch of other features.
    – Polynomial
    Commented Jan 19, 2014 at 22:08

2 Answers 2


Given your requirements, you'd be much better off sticking with WinDbg.

OllyDbg doesn't do .NET, nor is it capable of directly analyzing minidumps. It does have the ability to log its run traces, but this is likely not the type of logging that you need.

OdbgScript is nice, but it sounds like that's not enough of a reason for you to make the change.


OllyDbg is nice, and it has some cool features but it still doesn't support x64 native debugging on Window (it is in Alpha though!)

If you want to debug x64, then WinDbg seems to be the way to go.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.