qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Michael Roth <mdroth@linux.vnet.ibm.com>
To: "Gonglei (Arei)" <arei.gonglei@huawei.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] How to debug qemu-ga.exe (step by step) in windows ?
Date: Tue, 01 Apr 2014 10:06:16 -0500	[thread overview]
Message-ID: <20140401150616.22831.67995@loki> (raw)
In-Reply-To: <33183CC9F5247A488A2544077AF19020815DC917@SZXEMA503-MBS.china.huawei.com>

Quoting Gonglei (Arei) (2014-04-01 07:47:42)
> Hi,
> 
>     I'm learning qemu ga from wiki  http://wiki.qemu.org/Features/QAPI/GuestAgent
>     qemu-ga.exe is running in my windows VM now, and I want to debug it step by step.
>     Could anyone specify how to debug in windows ?  Thanks.

There's WinDbg, which is fairly well documented. I've used it from time to
time, but only for very basic things like getting the stacktrace from a crash.

Beyond that I've gotten by mostly by sticking g_print/g_warning() statements
everywhere until I track down whatever problem I'm looking for.

Theoretically, with the win32 serial port support recently added, you can
rebuild and test using this approach purely in a linux VM (with mingw
cross-build environment) via WINE by handing WINE the qemu-emulated serial
port... was going to suggest this approach but unfortunately, in FC18 at least,
there seems to be some issue with COM ports in WINE where the input to qemu-ga
just gets echoed back to the user/host rather than actually getting passed
through to qemu-ga..., but maybe it'll work for you/others.

That's the only real general advice I can offer, but maybe with more details
of what you're looking into I can be of more assistance.

> 
> 
> 
> Best regards,
> -Gonglei

      reply	other threads:[~2014-04-01 15:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-01 12:47 [Qemu-devel] How to debug qemu-ga.exe (step by step) in windows ? Gonglei (Arei)
2014-04-01 15:06 ` Michael Roth [this message]

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=20140401150616.22831.67995@loki \
    --to=mdroth@linux.vnet.ibm.com \
    --cc=arei.gonglei@huawei.com \
    --cc=qemu-devel@nongnu.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).