On Tue, 04 Sep 2001 16:37:14 -0700,
"Matt D. Robinson" <yakker@xxxxxxxxxxxxxx> wrote:
>"Schaal, Richard" wrote:
>> I used to work for Stratus Computer - at that time, a panic or oops would
>> put us into the debugger, and if we
>> were successful in patching up the problem, the system could resume
>> execution. In Linux, after an oops, maybe
>> a "nodump" command would be useful as well to disable the dumping that might
>> normally occur.
>
>This is fine -- I think these are all reasonable extensions to KDB, and
>I can work with that developer if need be to make that happen. There's
>an easy solution, one way or another.
No need to involve me. Any code can register its own kdb commands as
long as it runs after kdb init. IOW, the nodump command can be part of
lkcd, no changes to kdb required. Just wrap it in #ifdef CONFIG_KDB.
|