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-651-g2e96e91 Date: Sun, 25 Dec 2011 20:13:00 -0000 [thread overview] Message-ID: <20111225201314.5116.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 2e96e9163d84fe9772def0318216a6d6da1332a2 (commit) from 132b6fe86650df9cd1c684d133d7f815512cb519 (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 2e96e9163d84fe9772def0318216a6d6da1332a2 Author: Mark Wielaard <mjw@redhat.com> Date: Sun Dec 25 20:56:53 2011 +0100 Use function.call and function.return in all thread_indent() examples. If the .call modifier isn't used the function probes will match both .call and .inline, but .return doesn't match any inlined functions leading to unbalanced thread_indent output. ----------------------------------------------------------------------- Summary of changes: doc/SystemTap_Beginners_Guide/en-US/Scripts.xml | 2 +- doc/tutorial.tex | 12 +++++++++++- doc/tutorial/socket-trace.stp | 2 +- 3 files changed, 13 insertions(+), 3 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2011-12-25 20:13 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=20111225201314.5116.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: 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).