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] double fault ...

To: Gerd Knorr <kraxel@xxxxxxxxxxx>
Subject: Re: [Xen-devel] double fault ...
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Mon, 2 May 2005 16:23:42 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 02 May 2005 15:25:41 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20050502145143.GB15699@bytesex>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20050502145143.GB15699@bytesex>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

On 2 May 2005, at 15:51, Gerd Knorr wrote:

... happens with panics when compiled with debugging.
panic() calls debugger_trap_immediate(), which triggers
do_int3, which calls panic(), which recurses until the
stack is full => bang!

You compile with crash_debug=y? The intention is that do_int3() will execute DEBUGGER_trap_fatal() before panic(), so you should enter the gdb stub rather than infinitely loop. How is that not occurring?

 -- Keir


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

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