public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: mark@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.6-312-ga09fc5a
Date: Thu, 13 Oct 2011 21:36:00 -0000	[thread overview]
Message-ID: <20111013213603.1138.qmail@sourceware.org> (raw)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "systemtap: system-wide probe/trace tool".

The branch, master has been updated
       via  a09fc5a45fef1aaf1fca5b02574c9d0e4890e96f (commit)
      from  2ec6b38c60450db5d94323284d53978ea9c2bf1f (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit a09fc5a45fef1aaf1fca5b02574c9d0e4890e96f
Author: Mark Wielaard <mjw@redhat.com>
Date:   Thu Oct 13 23:19:21 2011 +0200

    Handle PPC64 function symbols by resolving function descriptors.
    
    * translate.cxx (dump_symbol_table): If the module is EM_PPC64, but not
      ET_REL, then register two address for a STT_FUNC. The function descriptor
      address and the address of the function that the descriptor points to.
      For ET_REL still rely on the .function_name convention.

-----------------------------------------------------------------------

Summary of changes:
 translate.cxx |   64 +++++++++++++++++++++++++++++++++++++++++++++++++-------
 1 files changed, 56 insertions(+), 8 deletions(-)


hooks/post-receive
--
systemtap: system-wide probe/trace tool


                 reply	other threads:[~2011-10-13 21:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20111013213603.1138.qmail@sourceware.org \
    --to=mark@sourceware.org \
    --cc=systemtap-cvs@sourceware.org \
    --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).