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-58-g4645e3a Date: Wed, 03 Aug 2011 17:33:00 -0000 [thread overview] Message-ID: <20110803173321.23382.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 4645e3acc91160c5e866adfcda12ba00b7b3db0e (commit) via 1a0d7e04fc1480917cad9502aa7da3a102e29016 (commit) from 1a050f8213c1ff575a4d32cf690a3f0092caf780 (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 4645e3acc91160c5e866adfcda12ba00b7b3db0e Author: Mark Wielaard <mjw@redhat.com> Date: Wed Aug 3 19:30:37 2011 +0200 testsuite warn_overflow be more precise and a bit more lenient. log exactly once for syscall probe hit and counter i == 256. But do allow more than 3 overflow warning messages to occur in case stap miraculously recovers and overflows immediately afterwards. commit 1a0d7e04fc1480917cad9502aa7da3a102e29016 Author: Mark Wielaard <mjw@redhat.com> Date: Wed Aug 3 19:29:24 2011 +0200 testsuite warnings.stp: match all lines in bio_init@fs/bio.c:*. Since we aren't actually interested in the probe itself, and different kernels have different lines that can be probed, just match them all. ----------------------------------------------------------------------- Summary of changes: testsuite/systemtap.base/warn_overflow.exp | 4 +++- testsuite/systemtap.base/warn_overflow.stp | 2 +- testsuite/systemtap.base/warnings.stp | 2 +- 3 files changed, 5 insertions(+), 3 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2011-08-03 17:33 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=20110803173321.23382.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).