Moo Kim wrote:
Here is the output from lcrash of the trace command ... I called panic when
the rmmod was done
>> trace e000000049420000
================================================================
STACK TRACE FOR TASK: 0xe000000049420000 (rmmod)
0 dump_execute+380 [0xe00000000071b9dc]
1 panic+508 [0xe0000000005bfc9c]
this trace seems correct .... What part of lcrash is not working in
analyzing modules ??
> I somehow assumed that lcrash was capable of debugging
> kernel modules. I guess not. Is it possible to
> incorporate Dave's patch into lcrash distribution
> because it will be extremely useful for kernel module
> developer ?
>
> Thanks,
>
> Moo Kim Moo.Kim@xxxxxxx
> NCR Corporation
>
> On Wed, Mar 14, 2001 at 11:49:04AM -0600, Dave Craft wrote:
> >
> > >You can't use a module to call panic(). lcrash isn't capable (yet)
> > >of debugging kernel modules. The resulting crash dump may not be
> >
> > Regarding the above statement about inability to
> > debug kernel modules. Did you guys ever get around
> > to looking/rewriting the patch I supplied for getting tracebacks
> > in kernel modules? The patch still applies and still
> > works. Its buried in the archives of this mailing list.
> >
> > Is there any idea on when we'd see comparable
> > function make it into lcrash?
> >
> > --
> > Mail : dave@xxxxxxxxxxxxxx Phone : 512-838-8248
> > I am Jack's email closing
--
==========================================================================
Ken Pearlstein Field Tech Support Analyst
cell phone 703-362-9793 pager 888 308-0734
C/O SILICON GRAPHICS pearlste@xxxxxxxxxxxxxxxxxxx
14160 NEWBROOK DRIVE, SUITE 100 voice: (703) 227-8531 430-5403
CHANTILLY, VA 20151 fax: (703) 277-8500 430-5403
=========================================================================
|