From: Olaf Hering <olaf@aepfle.de>
To: Adel Amani <adel.amani66@yahoo.com>
Cc: xen-devel@lists.xen.org
Subject: Re: function snprintf() in xen_save_domain.c for debugged
Date: Fri, 7 Feb 2014 23:22:47 +0100 [thread overview]
Message-ID: <20140207222247.GA23234@aepfle.de> (raw)
In-Reply-To: <1391807749.53657.YahooMailNeo@web161801.mail.bf1.yahoo.com>
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
next prev parent reply other threads:[~2014-02-07 22:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-02 8:51 function snprintf() in xen_save_domain.c for debugged Adel Amani
2014-02-02 10:00 ` Olaf Hering
2014-02-03 12:56 ` Adel Amani
2014-02-03 13:11 ` Olaf Hering
2014-02-05 6:50 ` Adel Amani
2014-02-05 12:39 ` Olaf Hering
2014-02-06 12:28 ` Adel Amani
2014-02-06 21:40 ` Olaf Hering
[not found] ` <1391807749.53657.YahooMailNeo@web161801.mail.bf1.yahoo.com>
2014-02-07 22:22 ` Olaf Hering [this message]
[not found] ` <1392796739.73315.YahooMailNeo@web161801.mail.bf1.yahoo.com>
2014-02-19 14:12 ` Olaf Hering
2014-02-21 7:18 ` Adel Amani
2014-02-21 9:30 ` Olaf Hering
2014-02-21 16:34 ` Adel Amani
2014-02-24 9:02 ` Olaf Hering
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=20140207222247.GA23234@aepfle.de \
--to=olaf@aepfle.de \
--cc=adel.amani66@yahoo.com \
--cc=xen-devel@lists.xen.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).