After the fall of the Soviet Union some Russians imigrated to Germany... Many of those were well-educated, engineers etc. Maybe Olly is one such immigrant?
......
Ollys English is fluent, which is not usual with russians (language was not really one of the major subjects at school because travel was erstricted). This might mean two things: either he learned it by working with computers or he's been to germany longer than from 1990.....
Hopefully I will have more time now for version 2.0. Currently I'm working on analyzer. Global prediction of the contents of registers and stack is practically finished. This was a very hard piece, and initially veeery slow, but today I've found the way to accelerate it by the factor 100+. Next I plan to implement known functions. Debugging engine will follow.
Of course, OllyDbg 2.0 will work on all existing versions of 32-bit Windows: 95, 98, ME, NT4, 2000 and XP. I don't know whether it will make sense to play with Server 2003 at all, and Longhorn is not yet ready.
Several weeks ago I've asked for help in the form of different Windows versions that I'm going to use for debugging purposes. Honestly, I haven't hoped for so many offers:
Windows 98 and/or 98 SE
Windows ME (Tony, this was a nice gift!)
Windows 2000 home and/or professional (thank you, Rudy! No such thing as a home edition?)
Windows XP home and/or professional (thank you, Peter!)
Windows Server 2003 (many thanks, Casey!)
And my very special thanks to Reinhard - his post completed my collection! So please send me no more Windows, now I have them all :)
2.0 版FAQ:
Uh-oh, how many times have I promised to update this list? Enough, no more promises!
1. When will you release the new version of OllyDbg? - I can't tell you when first beta of v2.00 will be ready.
2. Please keep OllyDbg free! - I have no intentions to make OllyDbg commercial, even in second version. It is rated as a shareware for copyright reasons only.
This is the last beta. There will be no more new features. For about two weeks I will update the documentation and wait for your bug reports. If nothing unforeseen will happen, I will make final release, close this project and renew my work on v2.0.
New features:
Now you can set analysis hints to force decoding of some byte sequences. To set hint, select piece of code or data and from the pop-up menu choose Analysis|Treat selection as, then your selection. Selections in singular form set hint only on the first byte, in plural - repeatedly on the whole selection. Proposed by Eric Simmons and others. First I answered that this feature would be too significant for v1.10; now, after considering all possibilities, I've found more or less safe way to do this. Please check!
If debugged DLL has entry point, OllyDbg makes first pause on this entry point, then in LOADDLL.EXE. Proposed by Richard Ginzburg.
Disassembler will display, on your request, RET instead of RETN. Proposed by Ib Larsen.
Run Trace window now supports syntax highlighting. Proposed by X Shadow.
If command uses immediate constant that points to valid command in code, Disassembler adds menu item "Follow immediate constant". Proposed by KolAn and Paul Guerra.
New copy-to-clipboard options: whole Information pane, line of Run trace window. Proposed by sett07.
Option to mark DLL as system or non-system. Important for Run trace where you may request to trace over calls to system DLLs.
If doubleword in Stack points to stack, press Enter to follow it. Proposed by CoDe_Inject.
Maximal length of argument string is changed from 1024 to 4096 characters. Requested by BlackArT.
New CPU option: now you can specify the number of lines visible after current command during stepping and tracing. Proposed by Phong Tran and others.
ODBG_Pausedex(reasonex,extmode,registers,debugevent) extends functionality of ODBG_Paused(reason,registers). Many requests. Extended flags in reasonex proposed by Richard.
Listmemory() is now exported. Requested by lixg00.
There are many more requests in my list, but, unfortunately, they will not appear in the final release. Usually this is due to their complexity that may aversely influence the reliability of v1.10. I have transferred all such requests to the list of wishes for version 2.0. Sorry.
Removed bugs:
Registers menu option "Copy all registers to clipboard" now copies EAX, too. Reported by many contributors.
In code with non-standard alignment of sections, analysis and displayed code were desynchronized, so click on some line selected different line. Reported by comrade.
Menu "Follow in Dump" now displays more intuitive items if one of operands is implicit stack location (like in PUSH). Reported by Jacob Benoit.
OllyDbg now correctly disassembles VxDCall and VxDJump used by Win95 drivers. However, it assembles them to the same code. In almost improbable case that anybody will use this pseudocommand, user must correctly set bit 0x00008000 to distinguish between call and jump. Reported by Jacob Benoit.
OllyDbg compiled REP STOS FWORD [EDI] and similar nonsense to REP STOS DWORD [EDI]. Reported by Paul Guerra.
OllyDbg now adds "Open with OllyDbg" to Explorer's menu in DLLs. Reported by Truong Quoc Ngan.
Names window sometimes lost its contents after new modules were loaded. Reported by William Whistler.
If your bug is not here, this means that I was unable to reproduce it. In this case, please send me the detailed, step-by-step, sequence of actions. Don't forget to mention the version of your OS!
我感觉中国没有nt调试器的最主要原因就是大家太经济了,呵呵
