Keith,
Lkcd could very well register kdb command and do what ever. However, when
lkcd is linked into the kernel (which is the case most of the time), how
can it be sure that kdb is initialized before lkcd's init (where in it
could call kdb_register()) ?
Is there any other way to ensure correct ordering of init calls, besides
linking the objects in the desired sequence in the Makefiles?
Regards.. Vamsi.
Vamsi Krishna S.
Linux Technology Center,
IBM Software Lab, Bangalore.
Ph: +91 80 5262355 Extn: 3959
Internet: r1vamsi@xxxxxxxxxx
Keith Owens <kaos@xxxxxxxxxx> on 09/05/2001 05:17:31 AM
Please respond to Keith Owens <kaos@xxxxxxxxxx>
To: "Matt D. Robinson" <yakker@xxxxxxxxxxxxxx>
cc: "Schaal, Richard" <richard.schaal@xxxxxxxxx>, lkcd@xxxxxxxxxxx (bcc:
S Vamsikrishna/India/IBM)
Subject: Re: LKCD + KDB ?
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.
|