From: Shrinand Javadekar <shrinand@gmail.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Kernel symbol table
Date: Thu, 09 Apr 2009 20:28:00 -0000 [thread overview]
Message-ID: <fe51cfa60904091159g41fe41d7wc8afbf6a392d9fd5@mail.gmail.com> (raw)
In-Reply-To: <49DE4219.9020606@vmware.com>
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.
-Shri
On Thu, Apr 9, 2009 at 11:44 AM, Michael Snyder <msnyder@vmware.com> wrote:
> Shrinand Javadekar wrote:
>>
>> Hi All,
>>
>> I have gdb attached to a running kernel. Even if the kernel was not
>> built with symbols, there should be some symbols exported by the
>> kernel right? The ones exported by using EXPORT_SYMBOL; e.g. sys_open,
>> sys_close, etc.
>>
>> I believe these symbols are kept in the kernel symbol table. The
>> question I have is, how do I access this symbol table?
>>
>> Also, does the kernel do anything special about where to keep (at what
>> address) this symbol table?
>>
>> Thanks in advance.
>> -Shri
>
> Shri,
>
> If you build the kernel, the symbol file will be called "vmlinux"
> in the top level of your build tree. This is an elf file that gdb
> can read.
>
> You do not want the compressed file called "vmlinuz" (note 'z').
> That file is not elf.
>
> Cheers,
> Michael
>
>
--
Discover the 'web' of videos
www.videonym.com
next prev parent reply other threads:[~2009-04-09 19:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-09 16:34 Shrinand Javadekar
2009-04-09 19:00 ` Michael Snyder
2009-04-09 20:28 ` Shrinand Javadekar [this message]
2009-04-09 20:36 ` Michael Snyder
2009-04-09 20:50 ` Shrinand Javadekar
2009-04-09 20:52 ` Michael Snyder
2009-04-10 1:21 ` Baurzhan Ismagulov
2009-04-13 3:11 ` Jan Kratochvil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fe51cfa60904091159g41fe41d7wc8afbf6a392d9fd5@mail.gmail.com \
--to=shrinand@gmail.com \
--cc=gdb@sourceware.org \
--cc=msnyder@vmware.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox