lkcd
[Top] [All Lists]

Re: snia lcrash questions

To: Ken Pearlstein <pearlste@xxxxxxxxxxxx>
Subject: Re: snia lcrash questions
From: Moo Kim <Moo.Kim@xxxxxxx>
Date: Wed, 14 Mar 2001 10:53:50 -0800
Cc: Moo Kim <Moo.Kim@xxxxxxx>, Dave Craft <dcraft@xxxxxxxxxxxxxx>, "Matt D. Robinson" <yakker@xxxxxxxxxxxxxx>, lkcd@xxxxxxxxxxx
In-reply-to: <3AAFB9A0.1A2A313E@xxxxxxxxxxxx>; from pearlste@xxxxxxxxxxxx on Wed, Mar 14, 2001 at 01:34:08PM -0500
References: <3AAFAC82.6FFB0C78@xxxxxxxxxxxxxx> <200103141749.LAA45332@xxxxxxxxxxxxxxxxxxxx> <20010314102514.L18766@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <3AAFB9A0.1A2A313E@xxxxxxxxxxxx>
Sender: owner-lkcd@xxxxxxxxxxx
User-agent: Mutt/1.2.5i
 Hello Ken,

 I was simply following up with Matt and Dave's email 
 below.   I have not tried out (yet) whether lcrash 
 is capable of debugging kernel modules.   If lcrash
 already supports kernel modules for analyzing panic 
 dumps as well as live debugging, that is a great news. 
 
 Thanks,

 Moo

On Wed, Mar 14, 2001 at 01:34:08PM -0500, Ken Pearlstein wrote:
> 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
> =========================================================================
> 

<Prev in Thread] Current Thread [Next in Thread>