For now, this is correct. Hopefully, this will change now that
we're moving to a new model of development -- we're removing most
of the dependencies on building 'lcrash' with the right header
files and moving to something more dynamic from a single object
header build.
Check out the latest stuff in the 2.4 tree.
BTW, Andi, did 2.4 change the scheduler now so that you don't have
to get tasklist_lock to avoid having jobs scheduled underneath you
(in a panic()/interrupt state)?
--Matt
Hari Kannan wrote:
>
> Isnt it true that lkcd cannot show stack backtraces for loadable modules?
>
> Hari
>
> >
> > On Fri, Nov 03, 2000 at 02:08:11PM -0800, Tom Morano wrote:
> > > It contains an example of how you to modify the sys_setpriority()
> > > function so that, it causes either a panic or a SEGV trap. There is
> > > also a sample program that calls setpriority() to initiate the dump.
> >
> > That sounds rather complicated. Why don't you just load a small kernel
> > module for it ?
> >
> > #include <linux/module.h>
> > int init_module(void)
> > {
> > panic("Dump");
> > }
> >
> >
> > gcc -O2 -DMODULE -c module.c
> > insmod module.o
> >
> >
> >
> >
> > -Andi
> >
|