Cool. Thanks for all the information. I'll just proceed with using the
cmd dir in 2.2 for now then. I'm banging away at lkcd on ide disk here
using the 1.1 beta.
On Wed, 15 Nov 2000, Tom Morano wrote:
> Hi Jay,
>
> The lkcdutils repository does exactly as you suspect, namely it
> separates the lcrash utility from the kernel source tree. If you look
> in the 2.4 tree, you will notice that, although the cmd directory tree
> still exists, it contains no files (the directories will be going away
> soon).
>
> The lcrash built from lkcdutils will work for both 2.2 and 2.4 kernels
> (it's still architecture specific, however). It will even work with
> different sub releases (e.g. 2.2.16 versus 2.2.18). The way we
> accomplish this is to use stabs type information generated for a
> particular kernel build. Since there currently is no type information
> generated by default, we have added a mechanism for creating a new
> target as part of our LKCD kernel patch. The Kerntypes target is a
> dummy .o built with -gstabs. It gets installed into the /boot
> directory, along with vmlinux and System.map. By accessing the stabs
> type informaiton contained in this module, we avoided the necessity of
> directly including kernel header files, and were able to remove lcrash
> from the kernel source tree. We plan to release an rpm that installs
> the lcrash binary, system scripts, and kernel patches necessary for
> implementing LKCD. All of this is work in progress. Matt and I are
> working to get this done ASAP.
>
> Regarding the lkcdutils build errors you encountered, one of those is
> newly introduced (by me) and is the result of my getting lcrash
> working for the ia64 architecture. The other one is a side effect of
> having a more up-to-date binutils package on your system. I will be
> checking in a fix for both of these problems today.
>
> Thank you for your interest. Please let us know if there is any
> functionality you would like to see added to this tool.
>
> Tom
>
>
> Jay Weber wrote:
> >
> > I've noticed the lkcdutils repository on sourceforge and am wondering if
> > somebody could update me as to what the status of it is. It appears to
> > seperate lcrash into the userland realm so that I don't have to build that
> > as part of my kernel package and that sounds great for packaging purposes.
> >
> > Does it work with 2.2 based kernel (or at all at this point)? When
> > compiling I'm getting:
> >
> > make[2]: Leaving directory `/usr/opt/build/BUILD/lkcdutils/lcrash/cmds'
> > gcc -o lcrash -static -rdynamic -L. -L/usr/src/linux -L./../libklib
> > -L./../liballoc -L./../librl main.o util.o eval.o report.o stabs.o
> > struct.o vmdump.o -lcmds -larch -lalloc -lrl -lklib -lncurses -lopcodes
> > -lbfd -liberty -ldl
> > ./libcmds.a(cmd_strace.o): In function `strace_cmd':
> > cmd_strace.c:63: undefined reference to `ia64_find_trace'
> > ./libarch.a(idis.o): In function `do_dis':
> > idis.c:104: undefined reference to `print_insn_i386'
> > collect2: ld returned 1 exit status
> > make[1]: *** [lcrash] Error 1
> > make[1]: Leaving directory `/usr/opt/build/BUILD/lkcdutils/lcrash'
> >
> > Looking at the 2.2 cvs tree, these print_insn_* funcs seem to exist. In
> > lkcdutils they don't.
> >
> > Thanks.
>
|