From: "Frank Ch. Eigler" <fche@redhat.com>
To: Roland McGrath <roland@redhat.com>
Cc: systemtap@sources.redhat.com
Subject: inconsistent module relocation in elfutils
Date: Fri, 04 Nov 2005 20:08:00 -0000 [thread overview]
Message-ID: <20051104200813.GA28901@redhat.com> (raw)
Hi, Roland -
As a part of my work with but #1329, I've found that different kernel
builds work differently with the same elfutils/systemtap code with
respect to module relocation. The 'kernel' module appears to work
consistently.
Specifically, with some kernel versions (e.g. 2.6.13-1.1532_FC4) I
find that the GElf_Shdr sh_addr fields of .text-like sections are
correctly relocated, and for other kernel versions (2.6.9-22.EL), that
field is left at zero. Can you suggest an explanation or workaround?
Test thusly (cvs systemtap, elfutils .116):
% stap -p2 -e 'probe module("nfs").function("init_nfs_fs") {}' -v |& grep skip
One can put a breakpoint at tapsets.cxx:1673 and look at variable "*shdr".
- FChE
next reply other threads:[~2005-11-04 20:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-04 20:08 Frank Ch. Eigler [this message]
2005-11-04 20:37 ` Roland McGrath
2005-11-08 9:42 Mao, Bibo
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=20051104200813.GA28901@redhat.com \
--to=fche@redhat.com \
--cc=roland@redhat.com \
--cc=systemtap@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).