From: Roland McGrath <roland@redhat.com>
To: Mark Wielaard <mjw@redhat.com>
Cc: prasad@linux.vnet.ibm.com, systemtap@sourceware.org,
Stan Cox <scox@redhat.com>,
dsmith@redhat.com
Subject: Re: Failures with exelib.exp testcase (was Re: minutes 2010-08-19)
Date: Thu, 20 Jan 2011 01:19:00 -0000 [thread overview]
Message-ID: <20110120011852.1C1041822E9@magilla.sf.frob.com> (raw)
In-Reply-To: Mark Wielaard's message of Wednesday, 19 January 2011 18:24:00 -0500 <1898521794.32834.1295479440812.JavaMail.root@zmail01.collab.prod.int.phx2.redhat.com>
> > I'm attaching the output of eu-readelf to this mail.
You always need -S output to make full sense of -s output.
> > Symbol table [37] '.symtab' contains 75 entries:
> > 56 local symbols String table: [38] '.strtab'
> > Num: Value Size Type Bind Vis Ndx Name
> > [...]
> > 61: 0000000010010a70 64 FUNC GLOBAL DEFAULT 22 print_hw
>
> So, that does match our _stp_symbol entry:
> { 0x10010a70, "print_hw" },
> and is also totally not what we want/need to resolve the address to
> the symbol name. I am not sure what is going on here.
I suspect that ...a70 is the fptr address rather than the code address. I
think that's what ppc64 has in st_value for STT_FUNC symbols. AIUI, the
word at address 0x10010a70 (i.e. the word in the file section+offset
corresponding to that virtual address) will hold the actual PC address.
I don't think there is any way other than looking at that stored word
to retrieve the real PC address for the function.
Thanks,
Roland
next prev parent reply other threads:[~2011-01-20 1:19 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100826194353.GC3185@redhat.com>
[not found] ` <20100827092840.GA4129@in.ibm.com>
[not found] ` <20100830032810.GA5213@in.ibm.com>
[not found] ` <1283152139.2362.2.camel@hermans.wildebeest.org>
[not found] ` <20100830111805.GA4115@in.ibm.com>
[not found] ` <1283169285.15128.20.camel@springer.wildebeest.org>
[not found] ` <20101111121023.GA2597@in.ibm.com>
[not found] ` <1289485749.2470.5.camel@hermans.wildebeest.org>
[not found] ` <20110117145437.GA4251@in.ibm.com>
[not found] ` <1295278356.2998.47.camel@springer.wildebeest.org>
2011-01-18 13:09 ` K.Prasad
2011-01-18 13:30 ` Mark Wielaard
2011-01-18 14:35 ` K.Prasad
2011-01-18 14:56 ` Mark Wielaard
2011-01-19 12:01 ` K.Prasad
2011-01-19 23:24 ` Mark Wielaard
2011-01-20 1:19 ` Roland McGrath [this message]
2011-01-20 11:11 ` Mark Wielaard
2011-01-20 18:53 ` Roland McGrath
2011-01-21 23:16 ` Mark Wielaard
2011-02-02 12:24 ` K.Prasad
2011-02-02 12:59 ` Mark Wielaard
2011-02-03 5:04 ` K.Prasad
2011-02-03 10:16 ` Mark Wielaard
2011-02-03 12:34 ` K.Prasad
2011-02-03 12:44 ` Mark Wielaard
2011-02-03 18:59 ` Roland McGrath
2011-02-08 13:13 ` Mark Wielaard
2011-02-08 18:45 ` Roland McGrath
2011-02-08 19:51 ` Mark Wielaard
2011-02-08 19:57 ` Roland McGrath
2011-02-14 16:50 ` K.Prasad
2011-02-14 20:33 ` Mark Wielaard
2011-03-04 7:13 ` K.Prasad
2011-03-04 15:06 ` Mark Wielaard
2011-03-17 9:05 ` K.Prasad
2011-03-17 13:04 ` 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=20110120011852.1C1041822E9@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=dsmith@redhat.com \
--cc=mjw@redhat.com \
--cc=prasad@linux.vnet.ibm.com \
--cc=scox@redhat.com \
--cc=systemtap@sourceware.org \
/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).