From: Kip Macy <kmacy@fsmware.com>
To: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: getting debug output from Xen during domain creation
Date: Sun, 22 Feb 2004 07:40:13 -0800 (PST) [thread overview]
Message-ID: <20040222073651.W84871@demos.bsdclusters.com> (raw)
In-Reply-To: <E1Aupff-0007bc-00@wisbech.cl.cam.ac.uk>
Well ...
1) MEM_LOG is gated by NDEBUG:
#ifndef NDEBUG
#define MEM_LOG(_f, _a...) \
printk("DOM%llu: (file=memory.c, line=%d) " _f "\n", \
current->domain, __LINE__, ## _a )
#else
#define MEM_LOG(_f, _a...) ((void)0)
#endif
2) I've checked the C preprocessor output - and the printf statements
are being generated.
3) Just for grins I've checked the output of strings on the object file
to make sure that the strings were in fact there.
I think something else is going on.
-Kip
On Sun, 22 Feb 2004, Ian Pratt wrote:
>
> > I've removed the DNDEBUG from xen/arch/i386/Rules.mk. However, during
> > a failed mmu_update I'm not seeing anything in /var/log/messages or any
> > output from xen_read_console.
>
> Try enabling MEM_LOG in xen/common/memory.c [*]
>
> This should probably be the default for DEBUG builds.
>
> Ian
>
> [*] Last time I looked, the macro was missing a '\' which you'll
> need.
>
>
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel
>
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
next prev parent reply other threads:[~2004-02-22 15:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-22 5:55 getting debug output from Xen during domain creation Kip Macy
2004-02-22 9:13 ` Ian Pratt
2004-02-22 15:40 ` Kip Macy [this message]
2004-02-22 16:16 ` Keir Fraser
2004-02-22 16:26 ` Kip Macy
2004-02-22 16:48 ` Keir Fraser
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=20040222073651.W84871@demos.bsdclusters.com \
--to=kmacy@fsmware.com \
--cc=Ian.Pratt@cl.cam.ac.uk \
--cc=xen-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.