public inbox for
help / color / mirror / Atom feed
Subject: [SCM] systemtap: system-wide probe/trace tool branch, jistone/stapdyn, updated. release-1.7-232-g91101b9
Date: Wed, 16 May 2012 00:02:00 -0000	[thread overview]
Message-ID: <> (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, jistone/stapdyn has been updated
       via  91101b9c2d0f896be6aee7ab97c37b6079f9fe40 (commit)
       via  002d7a983ee63d44fc302bd3ddbfa35849db2fd0 (commit)
      from  0c26033f4abcbee41fd2278b1c45e4975bddd1ad (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 91101b9c2d0f896be6aee7ab97c37b6079f9fe40
Author: Josh Stone <>
Date:   Tue May 15 16:41:22 2012 -0700

    stapdyn: Add semaphore handling to dynsdt
    To test data-offset handling, this patch fleshes out SDT semaphore
    support in the dynsdt test program.
    It actually required a bit of section gymnastics to figure out the raw
    file offset of the semaphore, mainly because of the padding between the
    load addresses of the text and data segments.
    This code appears to work fine tested on a small executable (the
    heapsort example, modified to gate on the semaphore).  For unknown
    reasons, it doesn't seem to work on the semaphored SDT in libpython.
    The semaphore address appears to be computed and value incremented
    correctly, but the instrumentation never fires.  The semaphore even
    appears already incremented with a simultaneous stap -DDEBUG_UPROBES,
    and that handler does fire on the python function probes.  This may be a
    case of dyninst failing silently, as it does with longjmp SDT, but more
    investigation is required...

commit 002d7a983ee63d44fc302bd3ddbfa35849db2fd0
Author: Josh Stone <>
Date:   Tue May 15 16:40:00 2012 -0700

    stapdyn: Use the renamed fileOffsetToAddr
    This is keeping up with dyninst.git master, basically just


Summary of changes:
 stapdyn/dynsdt.cxx  |   59 ++++++++++++++++++++++++++++++++++++++++++--------
 stapdyn/stapdyn.cxx |    2 +-
 2 files changed, 50 insertions(+), 11 deletions(-)

systemtap: system-wide probe/trace tool

                 reply	other threads:[~2012-05-16  0:02 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).