I have a x64 machine and want to install Windbg (x86). I went on http://msdn.microsoft.com/en-us/windows/hardware/hh852365.aspx to download the Debugging Tools. However, only Windbg (x64) was installed.
The reason why I want the x86 version is because I am having issues debugging x86 applications which I do not encounter when using Windbg (x86).
I had trouble finding it a couple weeks ago as well. Ultimately I went to windbg.org, which linked me to the download I wanted. Check it out and see if that's what you need.
Short answer is get the latest SDK or DDK (now called the WDK) for Windows. The newest version of the Debugging Tools are included in the latest of each of these.
Installation directory
These are the default installation directories for Debugging Tools for Windows:
C:\Program Files (x86)\Windows Kits\8.x\Debuggers\x64
C:\Program Files (x86)\Windows Kits\8.x\Debuggers\x86
Excerpt from: http://msdn.microsoft.com/en-us/library/windows/hardware/ff551063(v=vs.85).aspx
Start here for an overview of Debugging Tools for Windows. This tool set includes WinDbg and other debuggers. The driver development environment and the Windows debuggers are integrated into Microsoft Visual Studio.
•To set up the integrated environment, install Visual Studio and then install the Windows Driver Kit (WDK). Debugging Tools for Windows is included in the WDK. You can get the integrated environment here.
•If you don't need the WDK, you can get Debugging Tools for Windows as part of the Windows Software Development Kit (SDK) for Windows 8.1. You can get the Windows SDK for Windows 8.1 here.
•If you want to download only Debugging Tools for Windows, install the Windows SDK, and, during the installation, select the Debugging Tools for Windows box and clear all the other boxes.
Here gives the direct download links from Microsoft official.
Windbg for windows 7 - download
x86: http://download.microsoft.com/download/A/6/A/A6AC035D-DA3F-4F0C-ADA4-37C8E5D34E3D/setup/WinSDKDebuggingTools/dbg_x86.msi
x64: http://download.microsoft.com/download/A/6/A/A6AC035D-DA3F-4F0C-ADA4-37C8E5D34E3D/setup/WinSDKDebuggingTools_amd64/dbg_amd64.msi
Windbg for windows 10 (WinDbg 10.0.18362.1) - download
x86: https://download.microsoft.com/download/4/2/2/42245968-6A79-4DA7-A5FB-08C0AD0AE661/windowssdk/Installers/X86%20Debuggers%20And%20Tools-x86_en-us.msi
x64: https://download.microsoft.com/download/4/2/2/42245968-6A79-4DA7-A5FB-08C0AD0AE661/windowssdk/Installers/X64%20Debuggers%20And%20Tools-x64_en-us.msi
Windbg preview (WindbgX) from Microsoft Store
https://www.microsoft.com/store/p/windbg/9pgjgd53tn86
Source:
https://github.com/yanglr/advDotnetDebugging/blob/main/README.md
Related
I have an application that uses the OpenCV libraries. This application has to be installed on an old PC running Windows XP 32 bit. When running the application I got the error:
Kernel32.dll unable to import InitializeCriticalSectionEx
According to my searches, to fix this issue, I have to tell the compiler that the library will be used on Windows XP by setting the variable _WIN32_WINNT to 0x0501. I'm trying to apply the solution found in this entry in github, but I'm not very experienced with compilers and I'm having hard time to locate the files CMAKE_CXX_FLAGS and CMAKE_C_FLAGS. Can anyone explain me exactly what file I have to modify?
I'm using Visual Studio 2017 and Cmake on Windows 10.
I tried to use the toolset v140_xp in Visual Studio, but without success. At the end of the day, I got an old PC with Windows XP, installed Visual Studio 10 and tried to compile. The problem was that the latest version (3.4.1) won't compile for Windows XP. AFAIK, the most recent version of OpenCV that compiles for XP is 3.2. Probably it is possible to cross-compile it on Windows 10 using the v140_xp toolset, but I did not try as I already got the old XP with Visual Studio 10.
Recently I installed Visual Studio 2017 Enterprise along with WDK 10 for 1709 My workloads contained C++ workload. . My machine is a Windows 8.1 Pro with net framework 4.6.1. After installing the WDK I expected the templates to come in the Legacy section of Visual C++ but no legacy option is present in it. I don't understand what is the problem. Please help me.
Thanks in advance
I resolved the issue. It was due to a missing windows 10 SDK. Reinstallating the WDK with appropriate SDK solved the problem
Developing drivers to windows is quite interesting one will be exposed to advanced Operating System Concepts. The set up for the environment will be IDE
IDE - Visual Studio (https://visualstudio.microsoft.com/thank-you-downloading-visual-studio/?sku=Community&rel=16)
Compilers (WDK)
Debugger (WDK)
WDK contains both(https://go.microsoft.com/fwlink/?linkid=2085767). Latest Visual Studio(VS2019) will come along with the latest WDK(10, 1903 as of now).
Sometimes plugins might not work properly i.e integration issues between Visual Studio and WDk.
By going to the location "C:\Program Files (x86)\Windows Kits\10\Vsix\VS2019" and run VSIX installer.
Now in a new project, driver related templates are available.
Have to ask this question once again here as none of the replies I found solve the issue.
So the goal is to set up the debugger for Qt Creator on Windows 8.1 x64. Visual Studio 2015 Update 3 (Community) and Qt 5.7 32-bit are installed on the system. As far as I understand I need Debugging Tools For Windows, which are a part of the Windows SDK. Visual Studio seems to install Windows SDK, but it doesn't have debugging tools. If I look into "C:\Program Files (x86)\Windows Kits\10\Debuggers" I see only one folder there, which is "x64" (and I suppose there must have been "x86" for 32-bit Qt). That folder contains three .dll files and no cdb.exe.
I tried to install Windows Debugging Tools manually as a part of Windows SDK, downloaded from here, but when I run the installer it gives me the error:
I guess that's because VS already has Windows SDK. Should I uninstall some component from Visual Studio? But I really don't want to break it.
Any help is appreciated
I have Visual Studio 2013 running on Windows 7 Pro. I needed the Windows Driver Kit for a project so I downloaded and installed this WDK 8.1 Update (for Windows 8.1, 8, and 7 drivers).
In this case I had not installed components such as the Windows Driver Kit Version 7.1.0 before installing WDK 8.1 Update.
Now I do not see the build environments created anywhere so I am not sure if this version of WDK requires either an earlier version of WDK as well, if something went wrong during installation, or if Microsoft made changes to the build environments.
However, when I had the aforementioned Windows Driver Kit Version 7.1.0 installed on another machine, it had created the build environments shown below.
Should the WDK 8.1 Update be sufficient on its own to create the build environments and if so, where can they be accessed?
Starting with Window 8 all tools (Debugger, Windows performance Tools, ADK, WDK) are installed under C:\Program Files (x86)\Windows Kits\VERSION and can be found under Windows Kits in the startmenu. Look a bit under your current position to access the Windows Kits folder.
I have a Windows 7 machine with Visual Studio 2005 SP1 installed. Using this, I build an application which loads a DLL at runtime compiled with VS2005 SP1 but on Windows XP. This fails, with the following error:
"...\foo.dll": The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail.
The DLL loaded is compiled against the debug CRT. The answer to this question hints that vcredist_x86.exe only contains release-versions of the CRT. I'm not sure if that is relevant in this case, since both my machine and the machine on which the DLL was compiled on both have the full VS2005 SP1 installed.
Should I attempt to rebuild the DLL on Windows 7 (I'd prefer not to), and will that cause the DLL to become unusable on the Windows XP machine?
Problem solved. The problem was that the Windows 7 machine did not have the KB971090 update which was installed on the Windows XP machine which built the DLLs. I had to explicitly tell Windows Update that I wanted to receive non-Windows updates in order to be able to install the update.