From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gerd Knorr Subject: Re: double fault ... Date: Mon, 2 May 2005 17:53:33 +0200 Message-ID: <20050502155332.GD15699@bytesex> References: <20050502145143.GB15699@bytesex> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Mon, May 02, 2005 at 04:23:42PM +0100, Keir Fraser wrote: > > 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? Yes. Mostly to get a xen binary without optimization and with full debug info, so I can easily lookup stuff using "objdump -dS xen-syms | less +/". > 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? I don't actually have a debugger attached, so DEBUGGER_trap_fatal aka __trap_to_cdb() instantly returns. Gerd -- #define printk(args...) fprintf(stderr, ## args)