I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below.
Diagnostic-Code: smtp; 550-5.7.1 {mx051} The recipient does not accept mails
from 't-online.de' over foreign mailservers 550 5.7.1 ( http://portal.gmx.net/serverrules ) (in reply to RCPT TO
command)
December 3, 2009 |
The last beta, with rudimentary help (and I hope to improve it in the release).
The only really new feature (commented out in the second beta) is debugging of child processes. Other
modifications are evolutional: much more stable (and tricky) debugging engine, more
known functions, more or less consistent support for UNICODE and UTF8
in dialogs and comments, many bugfixes. Please check this version thoroughly and don't forget to report all errors, including grammatical. The release will follow soon! |
March 28, 2009 |
The second beta. I've planned
that it will come with the more or less complete help file.
Unfortunately, I had no time to write it. Therefore there will be also
the third beta release... soon. There are many - over 20 - bugfixes in the beta 2, some of them are really critical. As promised, there are no significant changes, with two exceptions. The recognition of UNICODE strings is vastly improved, they are no longer limited to ASCII subset (option "Use IsTextUnicode()". Also I recognize strings in the UTF-8 format. By the way, if you have some small sample program with the free source that uses UTF-8 strings, please send it to me (together with the screenshot of displayed strings) so that I will be able to test OllyDbg. The second new feature is in the run trace. New option "Pause when EIP points to modified command" helps, for example, to find the real entry point of the SFX-ed code. Just don't forget to create backup first (or use another new option, Auto backup user code)! |
December 23, 2008 |
The first beta release. "Beta"
means that there will be no significant changes till the final v2.00.
Now it supports memory and hardware breakpoints. They are fully
conditional, and the number of memory breakpoints is unlimited. Fast
command emulation takes memory breakpoints into account. In fact, run
trace may be much faster than the full-speed run if the number of false
access violations is high. Active hardware breakpoints turn emulation
off, but this may change in the future. SSE registers are fully supported. OllyDbg understands all command set extentions up to SSE4. AMD's SSE5 is not supported, but as far as I know, there are no SSE5-capable processors yet. Help on command covers all FPU commands. Help on some registers and bits is also available. Autoupdate of dump windows may also be useful. |
August 21, 2008 |
Big update. Powerful run trace,
profiling, analysis, many small improvements and multiple bugfixes.
Support for AT&T syntax is experimental and limited to
disassembler. If you find any errors, please let me know! |
May 24, 2008 |
Internal emulation of simple
commands (Options|Run trace|Allow
fast command emulation) has made run and hit trace 15 (fifteen!)
times faster. On my Athlon 4000+, standard run trace executes 35000
commands per second. With the emulation on, OllyDbg traces 500000 commands! For simple
programs, this may be close to the real-time execution - in the
step-by-step mode, with the full protocolling. Emulation covers only the small subset of 80x86 commands - moves, PUSH/POP, arithmetical and boolean operations, comparisons, shifts, jumps, calls, returns and LEAs. No multiplications, prefixes, loops or string operations, no FPU or MMX; still, OllyDbg passes to the application less than two percents of commands. Frequently one uses run trace together with the run trace condition, like: "stop trace when EAX==0x123456". Up to now, the inetrpreter parsed conditional expression on each step. However, this was too slow for the accelerated trace. Now I compile expressions to the simple pseudocode and use a very quick interpreter to estimate the condition. As a result, the above comparison is processed in only 130 nanoseconds. Not bad! Oh yes, and command help now includes the string commands, too. |
May 8, 2008 |
Improved and bug-fixed debugging
engine. Help on all 8086 commands, except for string manipulations. |
April 19, 2008 |
Pre-alpha 5: hit trace! Maybe
you have tried to use hit trace in the version 1.10, only to discover
that it doesn't work with non-trivial programs. Hit trace in version 2
is different: instead of replacing all recognized commands with INT3, I set breakpoints
dynamically on all non-processed branches. It seems that 20-30 thousand
breakpoints is not a problem for the new debugger. Also in this
release: just-in-time debugging, command line, several bugfixes. Help
on command is ready for all non-SSE/non-FPU commands till LEA. |
March 11, 2008 |
Pre-alpha 4: name lists, search
for text strings, floating-point constants and intermodular calls, run
trace conditions, syntax highlighting (but default colours are not yet
set), pause on thread, names of the arguments on the stack etc. The
analysis of large modules is much faster now. |
December 25, 2007 |
Pre-alpha 3: many different
features like
attaching to running process, detaching, run trace (as yet without fast
stepping), real-time stack analysis, recognition of TLS callbacks,
guarded memory, intermodular calls etc. Look at the comment column in
the list of calls - you will enjoy it! |
October 20, 2007 |
Removed 5 bugs; strongly
improved functionality of existing windows; reduced number of false
switches |
October 09, 2007 |
First buggy pre-alpha code |