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