From: Michael Snyder <msnyder@vmware.com>
To: Shrinand Javadekar <shrinand@gmail.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Kernel symbol table
Date: Thu, 09 Apr 2009 20:36:00 -0000 [thread overview]
Message-ID: <49DE599B.8070702@vmware.com> (raw)
In-Reply-To: <fe51cfa60904091159g41fe41d7wc8afbf6a392d9fd5@mail.gmail.com>
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?
next prev parent reply other threads:[~2009-04-09 20:28 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
2009-04-09 20:36 ` Michael Snyder [this message]
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=49DE599B.8070702@vmware.com \
--to=msnyder@vmware.com \
--cc=gdb@sourceware.org \
--cc=shrinand@gmail.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