MS Windows Debuggers

• XP,2K,NT: The current debugger is at
  http://www.microsoft.com/ddk/debugging/installx86.asp
• ME: The Windows ME debugger is
  http://www.microsoft.com/ddk/debugging/download/WINMEDDK.EXE
• 95,98,NT: The Windows 2000 Platform SDK has a (very nice) GUI and remote (for kernels) debugger for Windows 9x & NT available free at http://www.microsoft.com/msdownload/platformsdk/windbg.htm (cache)
  • Note that if you are viewing a range of memory starting before a section that is committed and ending inside the section that is committed, all the memory will show as being undefined ("??" in place of values). For example, if you VirtualAlloc some memory with MEM_COMMIT and then point edi at the first byte of it and view edi-20 (so you can later see what was stosb'd to edi) the entire view will fill with "??" If "Reevaluate Expression Always" is enabled for the view, when edi advances enough that then entire view is defined, the ?'s will suddenly dissappear.

The debugger tool provided on the Windows 98 DDK is the Windows System Debugger (Wdeb386.exe) (docs). It requires a remote computer connected via a cable to the target computer. Debug binaries and components are provided for Windows 98 in the \dbg_sym directory on the Windows 98 DDK distribution CD.

TR for Win95(TRW) is a debugger running in WIN95. TRW can trace DOS COM,DOS EXE, DOS protect mode app,16bit NE,32bit PE programs. Multiple Breakpoint allowed. But it crashes the heck out of my machine.

W32Dasm is the user friendly Windows Program Disassembler/Debugger

http://www.crackstore.com/tools.htm many tools but NOT legal to use.

See

  .