Re: [lkcd-devel] Re: Re: lcrash and debian

Tom Morano wrote:

>----- Original Message -----
>From: "Corey Minyard" <[email protected]>
>To: "Tom Morano" <[email protected]>
>Cc: "Michael Holzheu" <[email protected]>; "Micah Anderson"
><[email protected]>; "Hariprasad Nellitheertha" <[email protected]>;
>"lkcd-devel" <[email protected]>;
><[email protected]>;
><[email protected]>
>Sent: Friday, October 01, 2004 7:47 PM
>Subject: Re: [lkcd-devel] Re: [lkcd-general] Re: lcrash and debian
>
>
>  
>
>>Tom Morano wrote:
>>
>>    
>>
>>>>crash has code for s390 and s390x.  I don't know if they work because I
>>>>don't have one of these beasts, but there is at least code there.
>>>>
>>>>
>>>>        
>>>>
>>>The version of crash that is in lkcdutils is very old. It was put there
>>>(years ago) as a place holder. At that time, there was some direct use of
>>>the gdb libraries it contained (we're talking about the version of lcrash
>>>before the arch independent version). I don't know if it makes sense to
>>>      
>>>
>even
>  
>
>>>keep this version of the source code around any more. It's quite large
>>>(because of the gdb source) and really bogs down the downloading of
>>>      
>>>
>project
>  
>
>>>source.  Also, If someone is interested in the crash source, they should
>>>      
>>>
>be
>  
>
>>>able to download a much more current version from RedHat...
>>>
>>>Tom
>>>
>>>
>>>      
>>>
>>Very true.  I am using the ones from Redhat with massive patches to make
>>then work cross.
>>
>>I would be willing to maintain the version in your CVS, if you like.  I
>>already maintain a CVS repository, it wouldn't be a big deal to move it.
>>
>>I'd also be willing to add my lkcdtools.
>>
>>    
>>
>
>Corey,
>
>I'm not sure the LKCD project is the best place for crash (it was only
>pushed into the LKCD tree because it wasn't clear where it was going to end
>up after MCL stopped supporting it). I may be off base on this as I don't
>use crash and am totally focused on lcrash. At the very least, I don't think
>it belongs inside of the lkcdutils tree. Ideally, I would like to see the
>two projects combine their efforts somewhat. I'm not sure if that's possible
>however. I would be interested in hearing input from others on this list
>regarding their preference.
>  
>
I really don't like lcrash because it is so tied to the kernel version.  
With crash, I can use the same tool to work on different versions with 
the same tool.  In an environment where I have to analyze crash dumps 
from lots of customers running on different kernel versions, different 
versions of LKCD (not to mention some using mcore), crash is much 
nicer.  I like the crash user interface better, too, especially the 
ability to do gdb operations with it.  The ability to nicely print 
arbitrary data structures is quite handy.

Plus, I have cross support for crash, which is also an absolute 
necessity for us since we support host development on different 
platforms than the target environment.

If I was to support this, I would maintain the one that does 
cross-development support, BTW.  I think there are enough people 
interested in this to make it worthwhile.

>Regarding your lkcdtools, this sounds like something that would make sense
>to include in the LKCD project. Right now, we are trying to get the tree
>synced up with what is shipping on SuSE SLES9 and get LKCD working with
>Debian. Beyond that, I'm focused on getting this working on SGI Altix (IPF)
>systems. The basic layout of the source and release mechanism is open for
>discussion. I would assume the same is true for the base level utilities
>themselves. This project is definitely in need of some more energy. Feel
>free to jump in... :]
>  
>
Probably the ugliest think about lkcdutils is building it.  It really 
needs to use autoconf/automake.  (So does crash, BTW).  But I don't have 
a lot of reason to fix that because I'm not using it any more.  I might 
work on fixing crash, but I have a lot of other things on my plate right 
now.

IMHO, lkcdutils doesn't need to exist any more.  Let Dave handle the 
crash dump support (with a little support from you) and use some simple 
tool for crash dump extraction like the one HP developed or lkcdtools.  
That way you can focus your energy on other things.

-Corey


-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl