Sorry, I am not yet clear. My understanding is:
1) System.map is created from vmlinux at kernel build time and placed
in /boot
2) /sbin/vmdump simply copies /boot/System.map to /var/vmdump at a
system boot time (i.e. _after_ a kernel panic, not when a panic
occurs)
So, I guess, as long as you do not rebuild vmlinux after you get a
vmdump, System.map can always be reproduced from the vmlinux you used
for the panicking system.
????
hiro
> -----Original Message-----
> From: Tachino Nobuhiro [mailto:tachino@xxxxxxxxxxxxxxxxxxxxx]
> Sent: Wednesday, July 18, 2001 19:19
> To: Hiro Sugawara
> Cc: 'Matt D. Robinson'; lkcd@xxxxxxxxxxx
> Subject: Re: Module support
>
>
>
> At Wed, 18 Jul 2001 14:49:23 -0700,
> Hiro Sugawara wrote:
> >
> > 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.
> >
>
> If you use lcrash with a live system, vmlinux is okay. But
> if you examine a saved crash dump, you need the System.map of
> the kernel
> which is running when panic occurred. You can retrieve symbol
> information from vmlinux, but current vmdump command saves
> only System.map.
>
> Am I missing something too :-)
>
|