Hey there,
I am trying to kernel debug using VMWare and WinDbg.
I've read some tutorials on how to set up the connection, but for some reason WinDbg can't connect, that's my problem.
That is what I have done:
I created a new serial port using this named pipe:
.\pipe\com1 This end is the server the other end is an application. Yield CPU on poll checked and of course connected.
I modified also the boot.ini like this:
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional - Debug " /Debug /fastdetect /debugport=
.\pipe\com1 /baudrate=115200
ok that's what I did with the VM
Then i power it on and started up WinDbg on my windows xp prof host.
Wanted to connect via com use pipe with
.\pipe\com1
The output is then always the following:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Opened
.\pipe\com1
Waiting to reconnect...
and Debugee not connected.
I tried already resynchronizyse and some other things, using a pipeutlitiy I can see that the pipe is available.
But why does it always say Debugee not connected although it is? I tried now with all settings around like 2 days and tried a lower baud too, but I always get this output not connected.
Edit: I am using latest windbg and latest VmWare Workstation
