diff options
author | Jason Wessel <jason.wessel@windriver.com> | 2010-05-21 04:04:26 +0200 |
---|---|---|
committer | Jason Wessel <jason.wessel@windriver.com> | 2010-05-21 04:04:26 +0200 |
commit | 5dd11d5d47d248850c58292513f0e164ba98b01e (patch) | |
tree | fd3c5f27dd40d6a483483de3644ca060a5cafd75 /lib/syscall.c | |
parent | powerpc,kgdb: Introduce low level trap catching (diff) | |
download | linux-5dd11d5d47d248850c58292513f0e164ba98b01e.tar.xz linux-5dd11d5d47d248850c58292513f0e164ba98b01e.zip |
mips,kgdb: kdb low level trap catch and stack trace
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
exception.
Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
Acked-by: Ralf Baechle <ralf@linux-mips.org>
Diffstat (limited to 'lib/syscall.c')
0 files changed, 0 insertions, 0 deletions