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

From: Michael Snyder <msnyder at vmware dot com>
To: Shrinand Javadekar <shrinand at gmail dot com>
Cc: "gdb at sourceware dot org" <gdb at sourceware dot org>
Date: Thu, 09 Apr 2009 13:24:59 -0700
Subject: Re: Kernel symbol table
References: <fe51cfa60904081737o5d8a75f3m2e61fff268ba779c@mail.gmail.com> <49DE4219.9020606@vmware.com> <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?

Follow-Ups:
- Re: Kernel symbol table
  - From: Shrinand Javadekar

References:
- Kernel symbol table
  - From: Shrinand Javadekar
- Re: Kernel symbol table
  - From: Michael Snyder
- Re: Kernel symbol table
  - From: Shrinand Javadekar

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