The second version of the 32-bit debugger OllyDbg is redesigned practically from scratch. As a result, it is faster, more powerful and much more reliable than its predecessor. Well, at least in the future, because many useful features from the version 1.10 are not yet available in 2.00.
However, version 2.00 already contains many new features that were not available before. Among them:
- Full support for SSE instructions, including SSE3 and SSE4. SSE registers are accessed directly, without code injection;
- Execution of commands in the context of debugger, allowing run trace speed - with conditions and protocolling! - of up to 1,000,000 commands per second;
- Unlimited number of memory breakpoints;
- Conditional memory and hardware breakpoints;
- Reliable, analysis-independent hit trace;
- Analyser that recognizes the number (and sometimes the meaning) of the arguments of unknown functions;
- Detaching from debugged process;
- Debugging of child processes;
- Built-in help for integer and FPU commands;
- Option to pause on TLS callback;
- Option to pass unprocessed exceptions to the unhandled exception filter.
And now about my plans for the future. Probably I will convert OllyDbg to UNICODE. There are too many places where ASCII is not fully supported by Windows, like file names with extended charset or controls that don't receive WM_WCHAR. This will mean end for Win95 and WinME users. Those who use WinNT, 2000, XP and Win7 will notice nothing. Of course, plugins will be forced to UNICODE, too.
I plan to introduce experimental plugin support in the version 2.01. The interface is not yet defined. If you have written plugins for v1.10, please send me your ideas and suggestions now!
Version 2.01 will finally work under 64-bit Windows. Probably I will start developing 64-bit OllyDbg, but this depends on my free time.
It's slowly becomes a tradition: immediately after releasing a final version, I must post a bugfix! This time, I have missed a crash in the popup menu of the breakpoint window. Tittan and Jack were the first to report it!
And once again: no, this version does not work under Win64!
