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?
I have applied the following patches to the linux-2.4.20 tree:
kdb-v2.5-2.4.20-common-1 kdb-v2.5-2.4.20-i386-1
BTW. Great work on the debugger.
Thanks,
Rob
-- Rob Tarte Pacific CodeWorks 1347 Pacific Ave., Suite 202 Santa Cruz, CA 95060 (p) 831-426-7582 (f) 831-426-7584
