| To: | Hiro Sugawara <hsugawar@xxxxxxxxxxx> |
|---|---|
| Subject: | Re: Module support |
| From: | Tachino Nobuhiro <tachino@xxxxxxxxxxxxxxxxxxxxx> |
| Date: | Wed, 18 Jul 2001 11:27:17 +0900 |
| Cc: | lkcd@xxxxxxxxxxx, Les Smith <lessmith@xxxxxxxxxxx>, Raghaua Vatsavayi <rvatsava@xxxxxxxxxxx> |
| In-reply-to: | <F13508319A1CD41187DE00508BACED6A020673AE@xxxxxxxxxxxxxxxxx> |
| References: | <F13508319A1CD41187DE00508BACED6A020673AE@xxxxxxxxxxxxxxxxx> |
| Sender: | owner-lkcd@xxxxxxxxxxx |
| User-agent: | Wanderlust/2.5.8 (Smooth) EMY/1.13.9 (Art is long, life is short) SLIM/1.14.7 () APEL/10.3 MULE XEmacs/21.1 (patch 14) (Cuyahoga Valley) (i586-kondara-linux) |
Hi,
At Tue, 17 Jul 2001 12:32:35 -0700,
Hiro Sugawara wrote:
> BTW, I have always been thinking that the "System.map" argument is
> redundant. It could be replaced with a shell command line like:
>
> `nm vmlinux|awk --posix '{if ($1 ~ /c[[:xdigit:]]{7}$) print}'|sort|uniq`
> (Some nm's seem to use 64 bit addresses. So, do not put an assumption
> of an 8-digit address field)
>
> This way, lcrash would only need the module binary files (with debug
> information for the better, but not mandatory).
>
You cannot use vmlinux if it is replaced by kernel update or
any other reason. System.map is OK because it is saved with a crash dump by
vmdump.
I think module support requires the same function. You need the
symbol maps of modules which was actually loaded when a crash occurred.
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | RE: Module support, Hiro Sugawara |
|---|---|
| Next by Date: | Re: Module support, T.Ohno |
| Previous by Thread: | RE: Module support, Hiro Sugawara |
| Next by Thread: | Re: Module support, Andreas Herrmann |
| Indexes: | [Date] [Thread] [Top] [All Lists] |