From: Keith Owens <kaos@ocs.com.au>
To: "SATHISH.J" <sathish.j@tatainfotech.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Reg System.map file
Date: Mon, 13 Aug 2001 15:16:35 +1000 [thread overview]
Message-ID: <10876.997679795@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Mon, 13 Aug 2001 10:52:42 +0530." <Pine.LNX.4.10.10108131048560.31544-100000@blrmail>
On Mon, 13 Aug 2001 10:52:42 +0530 (IST),
"SATHISH.J" <sathish.j@tatainfotech.com> wrote:
>Does the System.map file contain only the addresses of kernel functions
>present at the boot time. What I mean is, suppose I insert a new driver
>into the kernel, Is there any way to show its addresses in the System.map
>file? Please help me out with this.
System.map contains addresses of all the external symbols in vmlinux.
It does not contain the address of module symbols because they vary.
If you want a combined map that contains both kernel and module
symbols, use ksymoops -s. That works best when you save the module
data after each module load and unload.
man ksymoops
man insmod, section KSYMOOPS SUPPORT IN MODUTILS.
next prev parent reply other threads:[~2001-08-13 5:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-01 14:37 Reg crash utility installation SATHISH.J
2001-07-02 22:19 ` Patrick O'Rourke
2001-07-03 8:52 ` Reg kdb utility SATHISH.J
2001-07-03 10:39 ` Balbir Singh
2001-08-02 9:37 ` Reg char device driver on linux SATHISH.J
2001-08-12 13:35 ` Reg:flow of system call in linux SATHISH.J
2001-08-12 14:10 ` Alan Cox
2001-08-13 5:22 ` Reg System.map file SATHISH.J
2001-08-13 5:16 ` Keith Owens [this message]
2001-08-21 9:02 ` Reg core dump of KDE-2 SATHISH.J
2001-08-21 14:29 ` Ignacio Vazquez-Abrams
2001-08-23 12:59 ` command source code SATHISH.J
-- strict thread matches above, loose matches on Subject: below --
2001-08-13 5:28 Reg System.map file Nitin Dhingra
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=10876.997679795@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=sathish.j@tatainfotech.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