public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: jistone@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.3-160-g448a86b
Date: Tue, 28 Sep 2010 22:49:00 -0000	[thread overview]
Message-ID: <20100928224906.18580.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  448a86b7ff08eea4c2ffda8ac3249cf3cbb2e041 (commit)
      from  a6ba0a7879f3efba0736c3516987c6dedc557218 (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 448a86b7ff08eea4c2ffda8ac3249cf3cbb2e041
Author: Josh Stone <jistone@redhat.com>
Date:   Tue Sep 28 15:41:52 2010 -0700

    Fix SDTv2 with separate debuginfo
    
    We had a case where the ".probes" section was found in the main binary,
    but then sdt_query::init_probe_scn got its Elf* by looking first via the
    debuginfo and then falling back to the executable.  So when we got the
    raw data pointer, it was using the wrong Elf* for that section.
    
    This fix is to let dwflpp::get_section return the Elf* in which it found
    the appropriate section, so init_probe_scn doesn't have to guess.
    
    * dwflpp.cxx (dwflpp::get_section): Add an optional Elf** return
      pointer, and fill it in if needed.
    * tapsets.cxx (sdt_query::init_probe_scn): Use that Elf* for the section.

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

Summary of changes:
 dwflpp.cxx  |   10 ++++++----
 dwflpp.h    |    3 ++-
 tapsets.cxx |    6 ++----
 3 files changed, 10 insertions(+), 9 deletions(-)


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


                 reply	other threads:[~2010-09-28 22:49 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=20100928224906.18580.qmail@sourceware.org \
    --to=jistone@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).