Ah, that's a very good point, Matt!
I've so far been working only with a live kernel and I've never
applied the lkcd kernel patch so that I did not create Kerntypes.
No wonder I could not find Kerntypes! I instead rebuilt my kernel
with -g. Yeah, the file size became over 4MB which is no good for
an embedded system, but I am still in the development stage.
What about my original question about the necessity of System.map?
I found the kernel Makefile actually uses nm to create it. So, as
long as the kernel image is available, it doesn't seem necessary.
In an embedded application like ours, it costs money to keel extra
files like System.map. So, I plan to modify lcrash so that it accepts
a vmlinux file or even a zImage file as the first argument, and a
compressed Kerntypes file as the third argument. It shouldn't be too
difficult to make lcrash automatically distinguish the file types
given to the command line.
hiro
> -----Original Message-----
> From: Matt D. Robinson [mailto:yakker@xxxxxxxxxxxxxx]
> Sent: Wednesday, July 18, 2001 13:45
> To: Hiro Sugawara
> Cc: lkcd@xxxxxxxxxxx
> Subject: Re: Module support
>
>
> If you don't have a Kerntypes file, you should build one. It is
> basically a .o file that includes linux/sched.h, but is built with
> -gstabs. It should be very easy to build (and if you have the
> LKCD patches installed, it's already built for you).
>
> Don't use 'vmlinux' as the Kerntypes (unless, of course, you're
> building your entire kernel with -gstabs). Otherwise, you're going
> to get some wierd results. :)
|