search for: show_stack_overflow

This series consists of improvements to Xen''s ability to print traces of its own stack, and specifically for the stack overflow case to be able to use frame pointers in a debug build. I have dev tested the series in debug and non-debug cases, with and without memory guards, and I believe that all the stack traces look correct (given the available information Xen has), and that the

This series consists of improvements to Xen''s ability to print traces of its own stack, and specifically for the stack overflow case to be able to use frame pointers in a debug build. I have dev tested the series in debug and non-debug cases, with and without memory guards, and I believe that all the stack traces look correct. However, I would greatly appreciate a second opinion on the

...d_cr4(); + regs->ds = read_segment_register(ds); + regs->es = read_segment_register(es); + regs->fs = read_segment_register(fs); + regs->gs = read_segment_register(gs); + + printk("CPU: %d\n", cpu); + _show_registers(regs, crs, CTXT_hypervisor, NULL); show_stack_overflow(cpu, regs->rsp); panic("DOUBLE FAULT -- system shutdown\n"); _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel

...olatile (                                 \ > diff -r cddd503fb254 -r 3ccf3e993d5d xen/include/asm-x86/processor.h > --- a/xen/include/asm-x86/processor.h   Wed Feb 24 11:10:09 2010 +0000 > +++ b/xen/include/asm-x86/processor.h   Wed Feb 24 11:11:05 2010 +0000 > @@ -532,6 +532,7 @@ void show_stack_overflow(unsigned int cp >  void show_stack_overflow(unsigned int cpu, unsigned long esp); >  void show_registers(struct cpu_user_regs *regs); >  void show_execution_state(struct cpu_user_regs *regs); > +#define dump_execution_state() run_in_exception_handler(show_execution_state) >  void sho...