From: Ralf Baechle on 25 Feb 2010 09:10
On Fri, Feb 12, 2010 at 04:35:34PM -0600, Jason Wessel wrote:
> The only way the debugger can handle a trap in inside rcu_lock,
> notify_die, or atomic_notifier_call_chain without a recursive fault is
> to have a low level "first opportunity handler" do_trap_or_bp() handler.
> Generally this will be something the vast majority of folks will not
> need, but for those who need it, it is added as a kernel .config
> option called KGDB_LOW_LEVEL_TRAP.
> Also added was a die notification for oops such that kdb can catch an
> oops for analysis.
> There appeared to be no obvious way to pass the struct pt_regs from
> the original exception back to the stack back tracer, so a special
> case was added to show_stack() for when kdb is active because you
> generally desire to generally look at the back trace of the original
> CC: Ralf Baechle <ralf(a)linux-mips.org>
> Signed-off-by: Jason Wessel <jason.wessel(a)windriver.com>
Acked-by: Ralf Baechle <ralf(a)linux-mips.org>
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Prev: [PATCH] Synchronization required before release the lock: sem_post/8-1.c