WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] getting debug output from Xen during domain creation

To: Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] getting debug output from Xen during domain creation
From: Kip Macy <kmacy@xxxxxxxxxxx>
Date: Sun, 22 Feb 2004 07:40:13 -0800 (PST)
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Sun, 22 Feb 2004 16:05:31 +0000
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: <E1Aupff-0007bc-00@xxxxxxxxxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
References: <E1Aupff-0007bc-00@xxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxx
> 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
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel