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/
Home Products Support Community News


Re: [Xen-devel] crash in trace.c with large extra_data

To: George Dunlap <George.Dunlap@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] crash in trace.c with large extra_data
From: Olaf Hering <olaf@xxxxxxxxx>
Date: Mon, 11 Jul 2011 16:44:05 +0200
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 11 Jul 2011 07:44:54 -0700
Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; t=1310395449; l=552; s=domk; d=aepfle.de; h=In-Reply-To:Content-Type:MIME-Version:References:Subject:Cc:To:From: Date:X-RZG-CLASS-ID:X-RZG-AUTH; bh=FYRlktq83Sj4JpYs3C1zVZ87Cug=; b=wT5t9N+dIUcqFmuEfgSEGn24ADsbpFcJXX5WZAQMWBx9ByhjYxKKlggZfCC3UHfP54U 0bliZGkZ6zDPZ4GUmVAA6uTB+gOIwYSXCICdCA7Suu1flDilWuSPYpMFNsDr4sb237RJ0 yGFFSuY4M0IyNF3w8ul5kNtlga/1YLyfDQM=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <CAFLBxZbBf=BwEA0q5xWPhikPrNki8j081dmAL44+LMBEVAhh3g@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20110711140256.GA23061@xxxxxxxxx> <CAFLBxZbBf=BwEA0q5xWPhikPrNki8j081dmAL44+LMBEVAhh3g@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.21.rev5535 (2011-07-01)
On Mon, Jul 11, George Dunlap wrote:

> The general idea is that callers of trace_var() *shouldn't* be calling
> with extra_words > TRACE_EXTRA_MAX.  It's an assert so that it breaks
> on debug builds, allowing programmers to fix the mistake (obviously
> mine in this case), but not on production builds.
> I suppose it could be changed into a warning of some kind instead.


a simple printk() would do it I think.

In this unfortunate case the system does not even reboot, need to find
someone to power cycle the box..


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>