I am trying to do windows kernel debugging with VirtualBox and WinDBG. But every time I hit a breakpoint the virtual machine CPU usage skyrockets and the CPU registers do not show up in WinDBG. Am I doing something wrong?
What I have done:
- In VirtualBox I forwarded
COM1to a named pipe
- In WinDBG File >
COMtab: Ticked the "Pipe" check box, and for the
Port = \\\\.\pipe\debug;
In WinDBG the debug session is found, and I can hit breakpoints, I can step through code, I can see the disassembled code in the "Disassembly window", and I can view memory locations in the "Memory window". But nothing shows up in WinDBG "Registers window".
The Host OS is Windows 10 and for the Virtual Guest OS i tried both Windows XP and Windows 7 both have the same issue.
I am really not sure where to look for answers to this issue, could anyone point me in the right direction ?
For anyone else having this issue or trying to learn kernel debugging i used parts from the following tutorials to get to where I am so far: