This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Kernel symbol table


Hi Michael,

If these are not loaded how can other (maybe even user written)
modules link to them?

For. e.g. I could write a simple driver which calls sys_open to open a
file. When the module is built/loaded, how does the linker/loader know
the address of sys_open?

-Shri

On Thu, Apr 9, 2009 at 1:24 PM, Michael Snyder <msnyder@vmware.com> wrote:
> Shrinand Javadekar wrote:
>>
>> Hi Michael,
>>
>> Thanks for the reply. However, there are a couple of problems with
>> looking at vmlinux.
>>
>> 1. When I haven't built the kernel myself, I don't have the vmlinux file.
>> 2. When I am remotely connected to a machine, I don't really have the
>> vmlinux file with me.
>>
>> Hence, rather that getting the info statically from file, it would be
>> great to read it directly from the memory of the target.
>
> Not possible, afaik. ÂThe symbol sections of the vmlinu[x|z] file
> are explicitly NOT loaded into memory.
>
> Or were you thinking about some sort of /proc-like mechanism?
>


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]