WineHQ

Debugging Tools for Windows

No Screenshot

Submit Screenshot
Debugging Tools for NT-Based Operating Systems

The debuggers in the Debugging Tools for Windows package can run on all NT-based operating systems. They can debug any applications, services, or drivers that run on these operating systems. They do not support Windows 95/98/Me.

The Debugging Tools for Windows package includes documentation on WinDbg, KD, CDB, and NTSD, along with tips on how to debug various kinds of drivers and applications, how to create and analyze a crash dump file, how to run a remote debugging session, and how to use debugger extension commands. This package also includes several additional debugging tools and support tools.

Debugging Tools for Windows supports debugging of:
  • Applications, services, drivers, and the Windows kernel.
  • Native 32-bit x86, native Intel Itanium, and native x64 platforms.
  • Microsoft Windows NT 4.0, Windows 2000, Windows XP, Microsoft Windows Server 2003, and Windows Vista.
  • User-mode programs and kernel-mode programs.
  • Live targets and dump files.
  • Local and remote targets.
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.

Application Details:

Version: 6.x
License: Free to use
URL: http://www.microsoft.com/whdc/...
Votes: 0
Latest Rating: Bronze
Latest Wine Version Tested: 3.2

Maintainers: About Maintainership

No maintainers. Volunteer today!

Link Debugging Tools for Windows Free Download dbg_x86.msi Free Download dbg_amd64.msi

Test Results

Old test results
The test results you have selected are very old and may not represent the current state of Wine.
Selected Test Results

What works

Tested with: Release version 6.11.1.404 - March 27, 2009

Command line (console) tools like kd, cdb.

The GUI debugger "windbg" is not usable at this point due to window paint/region update/message queue bug.
As soon as child windows are opened it spins in endless repainting loop.
Switching to MDI like View (Option) doesn't work either.
Child windows are constantly refreshed eating all CPU.

What does not

  • window management is broken (registers, locals ...), probably wine bug, endless WM_PAINT loop eating all CPU
  • command line window: doesn't accept commands when hitting enter, probably due to builtin richedit 2.0 bugs, needs native riched20.dll override
  • debugging multithreaded managed code is broken: it fails to get thread contexts at some point

Workarounds

What was not tested

n/a

Hardware tested

Graphics:

  • GPU:
  • Driver:

Additional Comments

Bug 10522 is still the big blocker

selected in Test Results table below
Operating systemTest dateWine versionInstalls?Runs?Used
Workaround?
RatingSubmitter
ShowopenSUSE Leap 42.2 x86_64Mar 01 20183.2N/A Yes YesBronzeRalf Habacker 
ShowArch Linux x86_64Jul 07 20131.6-rc4Yes No GarbageLara Maia 
CurrentFedora 10 x86_64Apr 12 20091.1.19Yes No GarbageAnastasius Focht 
ShowDebian GNU/Linux 4.x "Etch"May 18 20081.0-rc1Yes Yes Garbagean anonymous user 
ShowFedora 7Nov 17 20070.9.49.Yes No GarbageAnastasius Focht 

Known Bugs

Bug # Description Status Resolution Other apps affected
10522 Multiple applications encounter infinite WM_PAINT loop (Platform SDK tools) NEW View

Show all bugs

HowTo / Notes

HOWTO

Download and Install Debugging Tools for Windows

Use the Debugging Tools for Windows to debug drivers, applications, and services on Windows systems. Debugging Tools for Windows includes WinDbg, a powerful debugger with a graphical interface and a console interface, as well as the console-based debuggers NTSD, CDB, and KD. You can install the Debugging Tools as a standalone component from the Windows SDK:

Download Debugging Tools from the Windows SDK

1. Installation prerequisites

Winetricks will take care of all needed installation prerequisites and work around some problems.­

$ wget https://raw.githubusercontent.com/Winetricks/winetricks/master/src/winetricks

.NET Framework 2.0 Redistributables installation is needed as prerequisite:
­

$ bash winetricks -q dotnet20


2. Installation

 The Debugging Tools are listed in two places on the Installation Options screen in the Windows SDK Setup Wizard:

  • Select the Debugging Tools option under the Common Utilities if you want the x86 version of Debugging Tools and you are installing on an x86 computer. This option automatically detects the CPU architecture of the computer on which you are installing the tools and it is the fastest method of installing the tools.

  • Select the Debugging Tools option under the Redistributable Packages to download all three versions of Debugging Tools (x86, x64, Itanium).

After you select the appropriate Debugging Tools option as described above, clear the check boxes for the other options so that you do not install unnecessary items. The Common Utilities option downloads the Debugging Tools into a Debugging Tools for Windows folder under your Program Files folder. The Redistributable Packages option downloads the Debugging Tools to C:\Program Files\Microsoft SDKs\Windows\v7.1\Redist\Debugging Tools for Windows.

Unattended installation of Debugging Tools for Windows

For a super fast unattended installation use the following command line (assuming you downloaded the .msi):

 $ wine msiexec /i dbg_x86_*.msi /qn INSTDIR="C:\\Program Files\\Debugging Tools for Windows"

Failed to open \\.\com1, Kernel debugger failed initialization

If you're using the serial port as transport device you need to make sure Wine knows about the serial port. For instance, if COM1 is mapped to /dev/ttyS0 you'd have a symlink of the form $WINEPREFIX/dosdevices/com1 -> /dev/ttyS0.

Example (replace "ttyS0" with your serial device as seen in Linux):

$ ln -s /dev/ttyS0 ~/.wine/dosdevices/com1

You also need to make sure that you have proper access (write) permissions to the device. Example (replace "ttyS0" with your serial device as seen in Linux):

$ sudo chmod 0777 /dev/ttyS0

Now you should be able to talk over serial transport with target.

An internal debugger error (xxx) occurred in component 'UI Debug Create'

The debugger GUI displays an error on startup. The following console messages are an indication of the problem:

fixme:dbgeng:DebugCreate (0x1008514,0x1068f14): stub

­You need to override "dbgeng" component to use native version:

$ WINEDLLOVERRIDES="dbgeng=n" wine ./windbg.exe

­

Comments

Comments Disabled

Comments for this application have been disabled because there are no maintainers.
Back