public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: dsmith@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. rhel52-ga-371-gcdf6ed5 Date: Mon, 09 Jun 2008 20:31:00 -0000 [thread overview] Message-ID: <20080609203114.19214.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 cdf6ed559ae01a88691849b1f5690cac15c8d3ae (commit) from 46f7b6be8fcb252def4d0f7d5ea88f8c82fa647b (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 cdf6ed559ae01a88691849b1f5690cac15c8d3ae Author: David Smith <dsmith@redhat.com> Date: Mon Jun 9 14:50:18 2008 -0500 Fixed utrace probe '$syscall' handling. 2008-06-09 David Smith <dsmith@redhat.com> * tapsets.cxx (utrace_var_expanding_copy_visitor::visit_target_symbol): Calls 'syscall_nr' to get the value of '$syscall'. 2008-06-09 David Smith <dsmith@redhat.com> * x86_64/registers.stp (syscall_nr): Added syscall_nr function. * i686/registers.stp (syscall_nr): Ditto. ----------------------------------------------------------------------- Summary of changes: ChangeLog | 4 ++++ tapset/ChangeLog | 5 +++++ tapset/i686/registers.stp | 4 ++++ tapset/x86_64/registers.stp | 4 ++++ tapsets.cxx | 19 +++---------------- 5 files changed, 20 insertions(+), 16 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2008-06-09 20:31 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=20080609203114.19214.qmail@sourceware.org \ --to=dsmith@sourceware.org \ --cc=systemtap-cvs@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: linkBe 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).