| To: | lkcd@xxxxxxxxxxx |
|---|---|
| Subject: | Re: Module support |
| From: | Jyunji Kondo <j-kondo@xxxxxxxxxxxxxxx> |
| Date: | Thu, 19 Jul 2001 14:09:35 +0900 |
| In-reply-to: | <OF2774E48E.8BE7B288-ONC1256A8D.004CC6CA@xxxxxxxxxx> |
| References: | <OF2774E48E.8BE7B288-ONC1256A8D.004CC6CA@xxxxxxxxxx> |
| Reply-to: | j-kondo@xxxxxxxxxxxxxxx |
| Sender: | owner-lkcd@xxxxxxxxxxx |
> >Currently we are planning following procedure. > > > > 1. Extract symbols for debugging modules from > > dump file by using a new lcrash option or a > > dedicated command. > > Which symbols do you like to extract from the dump? For example, - __insmod_'MODULE NAME'_O'FULL PASS NAME OF MODULE FILE'_... - __insmod_'MODULE NAME'_S.text_... - __insmod_'MODULE NAME'_S.rodata_... - __insmod_'MODULE NAME'_S.data_... I think there are enough informations to resolve all of loaded modules' symbols. > As far as I know, the Linux system stores only information > about exported kernel symbols (ksyms). Usually only some > symbols of kernel modules are exported. Hence, your method > will likely miss the majority of symbol information for modules. If above-mentioned symbols are retrieved from the dump and written to a file in /proc/ksyms format, The ksymoops command produces modules' symbols (include which have unexported attribute) with using this file and merges them into System.map. Jyunji Kondo |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Module support, Tachino Nobuhiro |
|---|---|
| Next by Date: | Re: Module support, Keith Owens |
| Previous by Thread: | Re: Module support, Keith Owens |
| Next by Thread: | RE: Module support, Hiro Sugawara |
| Indexes: | [Date] [Thread] [Top] [All Lists] |