Messages in this thread | ![/](/images/icornerl.gif) | | Date | Tue, 12 Mar 1996 19:42:33 -0500 | From | "David S. Miller" <> | Subject | on debugging loadable modules... |
| |
I was thinking about the problems we are seeing with debugging loadable modules since their text/data symbols are determined at run time. Maybe we should try to implement something like this:
* Each module when it loads does a low-priority printk perhaps KERN_MODULE? Syslog/klog is told to place messages at this level to /var/adm/module.log or whatever. Basically the printk looks like this:
smc_ultra_module: Loading image at base vaddr 0xdeadbeef
Maybe /proc/modules or something like that can hold this information around while the machine is running also.
* Each module, at compile time has 'nm' run on it after it is built producing a zero-relative foo_module.map
* Ksymoops is modified to understand this scheme and then trace properly through kernel modules using either the proc filesystem entries (if the machine didn't die from the oops) or extracting the lines from /var/adm/module.log when the machine comes back up _and_ the module.map file.
What do people think? This idea sucks doesn't it?
Later, David S. Miller davem@caip.rutgers.edu
| ![\](/images/icornerr.gif) |