Kernel Debugger and WinDbg

This topic describes how to launch the Kernel Debugger (KD) or WinDbg for use in debugging exclusive apps.

Note WinDbg can only be used for kernel mode debugging on the Xbox One.

Obtaining KD or WinDbg

Install KD or WinDbg from http://msdn.microsoft.com/en-us/library/windows/hardware/ff551063%28v=vs.85%29.aspx if you don’t already have it on your PC.

Targeting an Exclusive App with KD or WinDbg

Prevent app tear down after a crash using the xbconfig tool to set the EnableKernelDebugging key to true.

xbconfig EnableKernelDebugging=true  

You can start KD from the command line using the following command (assuming the default installation path)

C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\kd -k net:port=50039,target=<your tools IP> -y  "C:\Program Files (x86)\Microsoft Durango XDK\xdk\symbols"  

You can start WinDbg from the command line using the same options as KD (assuming the default installation path):

C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\windbg -k net:port=50039,target=<your tools IP> -y  "C:\Program Files (x86)\Microsoft Durango XDK\xdk\symbols"  

The -k option is used to tell the debugger how to connect to your console. Always specify port 50039. You’ll also need the tools IP address of your console.

The -y option points the debugger at the debug symbols for the Title OS. These are installed to “C:\Program Files (x86)\Microsoft Durango XDK\xdk\symbols” by XDK setup. Be sure to include the quotes on the command line.

If an exclusive app is not yet running, KD and WinDbg will display waiting to reconnect… until an exclusive app is started.

Getting More Information

See http://msdn.microsoft.com/en-us/library/windows/hardware/hh406279(v=vs.85).aspx for more information on using KD.

See http://msdn.microsoft.com/en-us/library/windows/hardware/hh406283%28v=vs.85%29.aspx
for more information on using Windbg