From: "Frank Ch. Eigler" <fche@elastic.org>
To: Roland McGrath <roland@redhat.com>
Cc: systemtap@sources.redhat.com
Subject: Re: rfc patch for buildid < shlib base address
Date: Wed, 25 Feb 2009 02:53:00 -0000 [thread overview]
Message-ID: <20090225021519.GA18969@elastic.org> (raw)
In-Reply-To: <20090225015525.F244FFC380@magilla.sf.frob.com>
Hi -
On Tue, Feb 24, 2009 at 05:55:25PM -0800, Roland McGrath wrote:
> > On my i686 F10 box, elfutils 0.140 probing /lib/libc-2.9.so, the
> > buildid data logic results in an address that is smaller than the dwfl
> > relocation base address for the module. readelf indicates the
> > build-id .note section well before .text. [...]
>
> It is normal that the build ID note appear earlier than the .text section.
> What is not normal is that you should care about the .text section's
> location at all. For any non-ET_REL module, the sole relocation base
> should correspond to the beginning of its earliest PT_LOAD.
Yes, but it seems like elfutils 0.140 on this machine does not do that.
./stap -p4 --vp 033 -e 'probe process("/lib/libc-2.9.so").function("atoi").call {}' -w | grep 0x
parsed 'atoi' -> func 'atoi'
focused on module '/lib/libc-2.9.so = [0x7e73000-0x7fe6650, bias 0x0] file /usr/lib/debug/lib/libc-2.9.so.debug ELF machine i?86 (code 3)
[...]
dump_unwindsyms /lib/libc-2.9.so index=0 base=0x7e73000
Found build-id in /lib/libc-2.9.so, length 20, end at 0x7e63198
- FChE
next prev parent reply other threads:[~2009-02-25 2:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 2:16 Frank Ch. Eigler
2009-02-25 2:38 ` Roland McGrath
2009-02-25 2:53 ` Frank Ch. Eigler [this message]
2009-02-25 3:02 ` Roland McGrath
2009-02-25 22:15 ` Mark Wielaard
2009-03-16 5:20 ` Mark Wielaard
2009-03-16 6:16 ` Mark Wielaard
2009-03-16 6:32 ` Mark Wielaard
2009-03-16 17:28 ` Mark Wielaard
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=20090225021519.GA18969@elastic.org \
--to=fche@elastic.org \
--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).