Alternatives:

Here is a list of some existing alternative debuggers. We think all of them lack essential things that can be important for people who wants to have just a simple, convenient and compiler independent debugger for its own applications. The main disadvantarge for all of them is overcomplication, that oriented primary to reverse engineering purposes.

OllyDbg A good debugger-disassembler primary for reverse engineering. Detects many code instructions and their combinations. Graphicly shows jumps between instructions. Supports Borland's symbols. Continuously updated.
(c) Oleh Yuschuk, SHAREWARE

TurboDebugger A good but out of date debugger for the text-mode. Supports source level debugging but only for programmes compiled by Borland's compiler until version BCC5.5. No updates.
(c) Borland™, FREE

SoftIce A well-kwnown and pupular debugger for drivers and kernel analysis. Allows to trace instructions at the kernel level. Very expensive.
(c) NuMega™, SHAREWARE

IDA Pro Disassembler for reverse engineering. Used by antivirus specialists to analyse code of viruses and other malicious programs. Graphicly displays relations between functions.
(c) Datarescue™, SHAREWARE

WinDbg A stand-alone debugger that allows to debug remote applications through network. Understands several debugging formats. All versions, that I have tested, contain many bugs.
(c) Microsoft™, FREE

PEBrowse Interactive An overcomplicated debugger at machine level instructions and also at IL (Interpretation Language) for .NET platform, (as said in its documentation). Allows to view process sections in tree view (TreeView control). Has visual bugs, others not tested.
(c) Russell Osterlund, FREE

Attention: If You know any other worthy debugger, please, let us know about it.

Software Listings: