On Friday 16 November 2001 17:53, A V wrote: [...] > > Not sure what you mean... The object file image, or > > the loaded, linked > > and relocated result? > > I mean accessing loaded, linked and relocated module.
Well, all that remains after the loader has done it's thing is raw code, a bunch of symbol table entries, and possibly some other information that's required for unloading the module. Being that wasting kernel memory is a Very Bad Thing (TM), I'd be surprized if there's much "interesting" data left around. (That depends on what's interesting to you, of course! :-) Either way, I guess you'll have to study the kernel code to find out more, as it's probably not documented in any other way, and more importantly, it's "opaque" implementation stuff that may well change between kernel versions. [...] > > http://www.caldera.com/developers/gabi/latest/contents.html > > http://www.muppetlabs.com/~breadbox/software/ELF.txt > > I know and read the ELF documentation given by TIS. > But still i have doubt regarding modules. Ok. Same here - the details are in The Source. It might also be interesting to investigate what happens in the compiler and linker when you build kernel modules. //David Olofson --- Programmer, Reologica Instruments AB .- M A I A -------------------------------------------------. | Multimedia Application Integration Architecture | | A Free/Open Source Plugin API for Professional Multimedia | `----------------------------> http://www.linuxdj.com/maia -' .- David Olofson -------------------------------------------. | Audio Hacker - Open Source Advocate - Singer - Songwriter | `-------------------------------------> http://olofson.net -' -- [rtl] --- To unsubscribe: echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED] -- For more information on Real-Time Linux see: http://www.rtlinux.org/
