xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: ¤終於aware <250716708@qq.com>
To: "Wei Liu" <wei.liu2@citrix.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [help] problem with debuging/tools/ioemu-qemu-xen/xen-vl-extra.c
Date: Mon, 2 Jan 2012 18:15:06 +0800	[thread overview]
Message-ID: <tencent_485C08C7518FDF676D33E626@qq.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1890 bytes --]

The function do_savevm of /tools/ioemu-qemu-xen/xen-vl-extra.c is called when using 'xm save/restore' command.
    Just as you said, DBG is a wrapper around printf.
    I also added DBG in qemu_savevm_state(), but it didn't produce output info. Perhaps, its output was redirected to another place where I didn't relalize or to /dev/null because of unknown reason...

 
------------------ 原始邮件 ------------------
发件人: "Wei Liu"<wei.liu2@citrix.com>;
发送时间: 2012年1月1日(星期天) 晚上8:04
收件人: "¤?K於aware"<250716708@qq.com>; 
抄送: "wei.liu2"<wei.liu2@citrix.com>; "xen-devel"<xen-devel@lists.xensource.com>; 
主题: Re: [Xen-devel] [help] problem with debuging/tools/ioemu-qemu-xen/xen-vl-extra.c

 
On Sat, 2011-12-31 at 12:06 +0000, ¤?K於aware wrote:
> Hi everyone,
>     I added debug info in the function
> do_savevm of /tools/ioemu-qemu-xen/xen-vl-extra.c as follow:
>  
>  
> DBG("going to
> save...");                                                                                                                                              
> ret =
> qemu_savevm_state(f);                                                                                                                                           
> DBG("save finish...");  
>  
> only to see "going to save..." and "save finish..." in the log
> file,but I couldn't get the debug output in qemu_savevm_state(f)
> called by "do_savevm". Why not?
>  

What are you expecting to see? If you want to see debug output for
qemu_savevm_state(), you should add some code to do that.

I don't find any DBG() definition in ioemu directory. I guess DBG() is
your customized wrapper around printf(), so it prints whatever you tell
it to print, right?

Another suggestion for your debugging is that you can use gdb to connect
to qemu -- it is just a userspace program.


Wei.

[-- Attachment #1.2: Type: text/html, Size: 3942 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

                 reply	other threads:[~2012-01-02 10:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=tencent_485C08C7518FDF676D33E626@qq.com \
    --to=250716708@qq.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /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).