From 1c383a66a1790f73b4e9cecd5bd72e932f790944 Mon Sep 17 00:00:00 2001 From: InstantGratimification Date: Wed, 3 May 2017 09:55:28 +0000 Subject: [PATCH] Update windows-debugging.md --- debugging/windows-debugging.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/debugging/windows-debugging.md b/debugging/windows-debugging.md index 141a643d..bcd052a5 100644 --- a/debugging/windows-debugging.md +++ b/debugging/windows-debugging.md @@ -15,7 +15,7 @@ Debugging Windows code can be tricky in a virtualized environment. The guide bel User-mode debugging is usually straightforward if it can be done on one machine. Just duplicate your normal debugging environment in the VM. -Things get complicated if you need to perform kernel debugging or troubleshoot problems that only manifest on system boot, user logoff or similar. For that you need two Windows VMs: the *host* and the *target*. The *host* will contain [WinDbg](http://msdn.microsoft.com/en-us/library/windows/hardware/ff551063(v=vs.85).aspx) installation, your source code and private symbols. The *target* will run the code being debugged. Both will be linked by virtual serial ports. +Things get complicated if you need to perform kernel debugging or troubleshoot problems that only manifest on system boot, user logoff or similar. For that you need two Windows VMs: the *host* and the *target*. The *host* will contain [WinDbg](https://msdn.microsoft.com/en-us/library/windows/hardware/ff551063(v=vs.85).aspx) installation, your source code and private symbols. The *target* will run the code being debugged. Both will be linked by virtual serial ports. - First, you need to prepare separate copies of both *target* and *host* VM configuration files with some changes. Copy the files from **/var/lib/qubes/appvms/vmname/vmname.conf** to some convenient location, let's call them **host.conf** and **target.conf**. - In both copied files add the following line at the end: `serial = 'pty'`. This will make Xen connect VM's serial ports to dom0's ptys.