public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: scox@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-0.9.8-112-g0c3bfb1
Date: Fri, 26 Jun 2009 18:34:00 -0000	[thread overview]
Message-ID: <20090626183410.20469.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  0c3bfb1ef9f5415ec92afac94a72db5a827fa634 (commit)
      from  f0d57904d70d912ca3fc82eeaaacccdac0307a87 (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 0c3bfb1ef9f5415ec92afac94a72db5a827fa634
Author: Stan Cox <scox@redhat.com>
Date:   Fri Jun 26 14:28:46 2009 -0400

    Use_utrace_syscall_arg with sdt utrace probes to avoid i386 arg fetching problems.
    
    * tapsets.cxx (probe_table):  Add is_uprobe and is_utrace.
    (probe_table::convert_probe): Use _utrace_syscall_arg.
    (sdt_var_expanding_visitor): Add utrace_probe.
    (sdt_var_expanding_visitor::visit_target_symbol): Use _utrace_syscall_arg.

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

Summary of changes:
 tapsets.cxx |   31 ++++++++++++++++++-------------
 1 files changed, 18 insertions(+), 13 deletions(-)


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


                 reply	other threads:[~2009-06-26 18:34 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=20090626183410.20469.qmail@sourceware.org \
    --to=scox@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).