Re: function snprintf() in xen_save_domain.c for debugged

[Olaf Hering <olaf@aepfle.de>]

On Tue, Feb 18, Adel Amani wrote:

> Hi
> i know because a lot of product output in xen-4.1, no logger in xc_save.c
> i change code again according to "http://xen.1045712.n5.nabble.com/
> xen-unstable-tools-xc-restore-logging-in-xc-save-td5714324.html"
> But i don't know purpose Mr "patchbot" of 
> @@ -185,6 +183,13 @@ main(int argc, char **argv)
> i test again to code Mr "patchbot" without Consideration 
> @@ -185,6 +183,13 @@ main(int argc, char **argv)
> and result again no message :-( ....


All that is very imprecise, so we can not help.
Also read what I wrote: dont drop xen-devel@lists.xen.org

Olaf



> On Saturday, February 8, 2014 1:52 AM, Olaf Hering <olaf@aepfle.de> wrote:
> Please keep xen-devel@lists.xen.org in CC list.
> 
> On Fri, Feb 07, Adel Amani wrote:
> 
> > yes, for print data, function print_stats() in xc_domain_save.c should run
> and
> > work. I read in function and check.... But i don't know really why this don't
> > work!!! :-|... I test 'fprintf(stderr,"STDERR\n"); fprintf(stdout,"STDOUT\
> n");'
> > But again not answer :'(.....
> 
> Please make sure the self-compiled binary is actually used. Try this to
> verify: grep STDERR /usr/lib/xen/bin/xc_save (assuming the fprintf above
> is actually in the compiled code.)
> 
> > how boot the domU with 'initcall_debug'?! Are affect on total time?!
> 
> This is a kernel cmdline option. Please check the documentation about
> how to pass additional kernel parameters to a domU.
> 
> 
> Olaf
> 
>