Anonymous user
VMware: Difference between revisions
no edit summary
| [unchecked revision] | [unchecked revision] |
m (Fixed VMware capitalization) |
No edit summary |
||
Line 25:
If using these options, Workstation prints a message "VMware Workstation is listening for debug connection on port 8832." into the vmware.log file. Start a GDB session (using a copy of your kernel that includes debug information), then:
* target remote localhost:8832
Note that some versions of VMWare contain a bug: after you disconnect GDB from port 8832, VMWare will actually continue listening on port 8833 not 8832. The actual port can always be located by looking at the latest "Debug stub" entry in the vmware.log file:
<code>vmx| W110: Debug stub: VMware Workstation is listening for debug connection on port 8833.</code>
Standard gdb commands work in this mode (e.g. printing memory, backtrace). Note that this is a debug stub attached to the KERNEL, not a userspace program.
Line 38 ⟶ 42:
VMware products emulate a triple fault by resetting the machine. On beta products, however, a guest triple fault results in Bug 19580. Sometimes this represents a bug in VMware's emulation; usually, this represents a bug in your kernel.
===Compatibility with IDEs===
* IDA Pro supports debugging Windows kernels via the VMWare stub [https://www.hex-rays.com/products/ida/support/tutorials/debugging_gdb_linux_vmware.pdf]
* VisualKernel supports debugging Linux kernels from Visual Studio with VMWare gdb stub [http://visualkernel.com/tutorials/vmware/]
==See Also==
| |||