public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Collins, Tom" <Tom.Collins@Surgient.com>
To: gcc-help@gcc.gnu.org
Subject: runtime addresses of functions in shared objects
Date: Tue, 03 Jul 2001 18:34:00 -0000	[thread overview]
Message-ID: <A490B2C9C629944E85CE1F394138AF957FC4CD@bignorse.SURGIENT.COM> (raw)

Hello...

Is there a way to determine the runtime addresses of functions that
reside in shared object files?

I am writing a profiler for an application in which I supply the mcount,
mstartup, and moncontrol functions.  The mcount function obtains the
callers return address from the stack.  I have a small multi-threaded
(cloned) application that I have tested this on, and it works fine.

What I am wondering is what to do with shared objects.  Do they not 
undergo relocation when they are loaded?  If so, how do I find out
what those relocated addresses are for those functions in the shared
object?

Thanks

             reply	other threads:[~2001-07-03 18:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-03 18:34 Collins, Tom [this message]
2001-07-04  2:29 ` Ingo Krabbe

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=A490B2C9C629944E85CE1F394138AF957FC4CD@bignorse.SURGIENT.COM \
    --to=tom.collins@surgient.com \
    --cc=gcc-help@gcc.gnu.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).