Re: Using KVM for Windows kernel debugging

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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").

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.exe -y <my-symbols> -k <comport spec>

I get different errors from kd:

"Unable to read head of debugger data list, Win32 error 0n56"

Tom
-- 
Tom Parkin
www.thhp.org.uk
The worst moment for the atheist is when he is really thankful and has
nobody to thank /Rossetti/
--
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

[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux