KDB_REASON_CALL

[Keith Owens]

On Wed, 26 Feb 2003 10:45:47 -0800, 
Rob Tarte <robt at PacificCodeWorks.com> wrote:
>It seems that KDB_REASON_CALL doesn't give a stack backtrace anymore.
>I noticed kdb_local() used to build a register context with functions 
>like kdb_getcurrentframe()
>and kdba_setpc().  Now the code just says "kdb() called with no 
>registers, restricted function".
>Any particular reason?  Do I have the wrong patch?

For i386, kdb can sort of generate a stack frame, but it was always
flakey.  For ia64 it is not possible to generate a stack frame from
REASON_CALL.  Trying to support an environment without struct pt_regs
was causing lots of kdb problems and bugs, so I dropped the support.  I
strongly recommend that yoiu use KDB_ENTER() instead.  That generates
an interrupt and has registers.