Re: [Xen-devel] double fault ...

[Kip Macy <kmacy@xxxxxxxxxx>]

It shouldn't matter - you can attach the debugger after crash.


                        -Kip 

On Mon, 2 May 2005, Gerd Knorr wrote:

> 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 +/<addr>".
> 
> > 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
> 
> 

-- 
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan

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