kdb
[Top] [All Lists]

Re: can't enter KDB after panic?

To: Keith Owens <kaos@xxxxxxxxxxxxxxxxx>
Subject: Re: can't enter KDB after panic?
From: Ken Preslan <kpreslan@xxxxxxxxxxx>
Date: Fri, 23 Feb 2001 14:24:10 -0600
Cc: kdb@xxxxxxxxxxx
In-reply-to: <1967.982901563@xxxxxxxxxxxxxxxxxxxxxx>; from kaos@xxxxxxxxxxxxxxxxx on Fri, Feb 23, 2001 at 03:12:43PM +1100
References: <20010222173122.A8980@xxxxxxxxxxx> <1967.982901563@xxxxxxxxxxxxxxxxxxxxxx>
Sender: owner-kdb@xxxxxxxxxxx
User-agent: Mutt/1.2.5i
On Fri, Feb 23, 2001 at 03:12:43PM +1100, Keith Owens wrote:
> This patch renames the existing kdb panic to oops and adds panic.
> Because of the way that kdb is entered from the panic() routine, it has
> no valid exception frame.  kdb tries to synthesise an exception frame
> but that is tricky and does not always work.  If backtrace from panic
> says "not in kernel" then get the pid from the earlier message and do
> "btp pid" instead.  You can also get invalid kernel addresses due to
> the incorrect exception frame, ignore those messages.

Sweet!  Thanks for you help.


-- 
Ken Preslan <kpreslan@xxxxxxxxxxx>
Code Monkey
Sistina Software, Inc.


<Prev in Thread] Current Thread [Next in Thread>