Form [http://www.microsoft.com/whdc/devtools/debugging/debugstart.mspx]: ''"WinDbg provides source-level debugging through a graphical user interface and a text-based interface. WinDbg uses the Microsoft Visual Studio debug symbol formats for source-level debugging. It can access any public function's names and variables exposed by modules that were compiled with Codeview (.pdb) symbol files.

Form [http://www.microsoft.com/whdc/devtools/debugging/debugstart.mspx]: ''"WinDbg provides source-level debugging through a graphical user interface and a text-based interface. WinDbg uses the Microsoft Visual Studio debug symbol formats for source-level debugging. It can access any public function's names and variables exposed by modules that were compiled with Codeview (.pdb) symbol files.

Latest revision as of 01:00, 24 December 2013

Required or recommended tools for development and using KDE libraries and applications under MS Windows.

"Ever wondered which program has a particular file or directory open? Now you can find out. Process Explorer shows you information about which handles and DLLs processes have opened or loaded." (freeware, for all Windows versions) more

"Console is a Windows console window (cmd.exe) enhancement, useful for using when you depend on this shell, e.g. with msvc. Console features include: multiple tabs, text editor-like text selection, different background types, alpha and color-key transparency, configurable font, different window styles." (GPL, for Windows 2000 or newer) more

Form [2]: "WinDbg provides source-level debugging through a graphical user interface and a text-based interface. WinDbg uses the Microsoft Visual Studio debug symbol formats for source-level debugging. It can access any public function's names and variables exposed by modules that were compiled with Codeview (.pdb) symbol files.
WinDbg can view source code, set breakpoints, view variables (including C++ objects), stack traces, and memory. It includes a command window to issue a wide variety of commands not available through the drop-down menus. [..] It also allows you to remotely debug user-mode code.",

To change the postmortem debugger to WinDbg, run windbg -I. (The I must be capitalized.)

Debug messages (logs) generated by kDebug() and kWarning() are not visible on MS Windows unless application is compiled in so-called CONSOLE subsystem. To show these messages also in WINDOWS subsystem, you can use DebugView tool. The tool offers searching in logs, filtering them using wildcards and saving them to file. (freeware) more

A tool for checking dependency of shared libraries. This utility that scans any 32-bit or 64-bit Windows module (exe, dll, ocx, sys, etc.) and builds a hierarchical tree diagram of all dependent modules. (freeware) more

Process Monitor is an advanced monitoring tool for Windows that shows real-time file system, Registry and process/thread activity. Use it to discover what process is using given files (very useful knowledge since Windows can block these files). more

AutoRuns provides very comprehensive knowledge of auto-starting locations, shows what programs are configured to run during system bootup or login, and shows the entries in the order Windows processes them. These programs include ones in your startup folder, Run, RunOnce, and other Registry keys. more