All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vandrovec <petr@vmware.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Xavier Bestel <xavier.bestel@free.fr>, roland <devzero@web.de>,
	linux-kernel@vger.kernel.org
Subject: Re: VMWare Workstation 6 for debugging Linux Kernel (!)
Date: Fri, 20 Apr 2007 04:21:28 -0700	[thread overview]
Message-ID: <4628A238.3010602@vmware.com> (raw)
In-Reply-To: <p73r6qf49zc.fsf@bingen.suse.de>

Andi Kleen wrote:
> Xavier Bestel <xavier.bestel@free.fr> writes:
> 
>> On Fri, 2007-04-20 at 00:46 +0200, roland wrote:
>>
>>> We just quietly added an exciting feature to Workstation 6.0. I believe it 
>>> will make WS6 a great tool for Linux kernel development. You can now debug 
>>> kernel of Linux VM with gdb running on the Host without changing anything in 
>>> the Guest VM. No kdb, no recompiling and no need for second machine. All you 
>>> need is a single line in VM's configuration file.
>> I think qemu has the exact same feature.
> 
> It doesn't seem to work for x86-64 there though.

Hello,

Do you mean with qemu or with VMware?  Yes, we do not support replay 
with 64bit guests, but debug interface should just work.  Only gotcha is 
that for 64bit guest you need another option:

debugStub.listen.guest64 = "TRUE"

and then you need to attach gdb to port 8864 (*).  Unfortunately it does 
not seem possible to build gdb which would support 16bit/32bit code 
while using 64bit gdb on-wire format, so there are two interfaces.  And 
if you single-step switch from 64bit mode to 32bit mode or back, you 
also have to switch gdbs.  Yes, it is a bit unintuitive, and 
additionally one gdb silently ignores breakpoints set up by other gdb, 
so you need to keep breakpoints in sync between two gdbs yourself :-(

(*) If you are using gdb which has both 32bit and 64bit support, be sure 
to issue appropriate 'set architecture xxx' before 'target remote 
localhost:88xx' (i386:x86-64 for port 8864, i386 or i8086 for port 
8832).  Otherwise gdb is going to die complaining it could not parse 
remote reply.

				Best regards,
					Petr Vandrovec

P.S.: Yes, I'm associated with VMware.

  reply	other threads:[~2007-04-20 11:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-19 22:46 VMWare Workstation 6 for debugging Linux Kernel (!) roland
2007-04-20  7:16 ` albcamus
2007-04-20  8:42 ` Xavier Bestel
2007-04-20 10:27   ` Andi Kleen
2007-04-20 11:21     ` Petr Vandrovec [this message]
2007-04-20 11:44       ` Nigel Cunningham
2007-04-20 12:38       ` Andi Kleen
2007-04-20 11:21     ` Nigel Cunningham
2007-04-20 11:45     ` Avi Kivity
2007-04-20 11:50       ` Nigel Cunningham
2007-04-20 11:52         ` Avi Kivity
  -- strict thread matches above, loose matches on Subject: below --
2007-04-20 10:58 devzero

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4628A238.3010602@vmware.com \
    --to=petr@vmware.com \
    --cc=andi@firstfloor.org \
    --cc=devzero@web.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xavier.bestel@free.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.