On 08/18/2009 04:54 PM, Tom Parkin wrote:
Hi Vadim,
2009/8/18 Vadim Rozenfeld<vrozenfe@xxxxxxxxxx>:
Try to download symbols first.
Thanks for the tip, it gets me a bit closer -- although still not
fully up and running !
With the symbols installed, and the windbg symbol path set, the windbg
process doesn't exit, and does print "Connected to Windows XP ..."
(although the window status bar still reports "Debuggee not
connected").
did you try /break switch in boot.ini?
However, other than that I have similar behavior as previously
reported -- the target VM hangs on a black screen chewing CPU, and in
time the windbg process starts reporting "GetContextState failed...".
Furthermore, I tried using kd rather than windbg to attempt to connect
to the target machine:
kd and WinDbg use the same debug engine the only one difference is in
user interface. However, kd is much faster.
kd.exe -y<my-symbols> -k<comport spec>
I get different errors from kd:
"Unable to read head of debugger data list, Win32 error 0n56"
What is your guest OS? Are you sure you have correct symbols?
If you don't need live debugging, you can set up your system to generate
crash dump file and use it
for post-mortem debugging session.
Regards,
Vadim
Tom
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
