¤終於aware
2012-Jan-02 10:15 UTC
Re: [help] problem with debuging/tools/ioemu-qemu-xen/xen-vl-extra.c
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.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel