public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: jistone@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.3-178-g9a5fa20 Date: Mon, 04 Oct 2010 19:31:00 -0000 [thread overview] Message-ID: <20101004193119.25924.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 9a5fa202687b1fcf21ade555348dc300e795af55 (commit) from 0f95a66f820fa6912f6a648fd71115d8a2fcd852 (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 9a5fa202687b1fcf21ade555348dc300e795af55 Author: Josh Stone <jistone@redhat.com> Date: Mon Oct 4 12:26:30 2010 -0700 PR12081: Name procfs buffers based on a local index We shouldn't use probe->name for the buffers, as that name is not necessarily unique after our probe de-duplication efforts. Instead, we can use a simple index variable to get a unique name for each procfs probe. * tapset-procfs.cxx (procfs_derived_probe_group::emit_module_decls): Declare and use the buffers with a name based on a simple index. ----------------------------------------------------------------------- Summary of changes: tapset-procfs.cxx | 31 ++++++++++--------------------- 1 files changed, 10 insertions(+), 21 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2010-10-04 19: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=20101004193119.25924.qmail@sourceware.org \ --to=jistone@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).