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. release-1.3-172-g86229a5 Date: Fri, 01 Oct 2010 17:58:00 -0000 [thread overview] Message-ID: <20101001175805.11234.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 86229a5533de13b6ac6eeb34d9ea24e7cfb64faa (commit) from ad10b896abfd40c47b4fa452534dfcc89464c964 (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 86229a5533de13b6ac6eeb34d9ea24e7cfb64faa Author: David Smith <dsmith@redhat.com> Date: Fri Oct 1 12:56:54 2010 -0500 Fixed BZ634242 by always looking up pids in the global namespace. * runtime/uprobes2/uprobes.c (uprobe_get_tg_leader): Always look up the pid in the global pid namespace. From Roland McGrath <roland@redhat.com> (uprobe_fork_uproc): Ditto. From Roland McGrath <roland@redhat.com> (uprobe_report_clone): If two processes are are sharing the same memory space (CLONE_VM) don't remove probes, since that will remove the probes from both processes. * tapsets.cxx (emit_module_exit): Make sure we always look up pids in the global pid namespace, not in any private pid namespace. * runtime/uprobes-common.c (stap_uprobe_change_plus): Ignore EEXIST errors. ----------------------------------------------------------------------- Summary of changes: runtime/uprobes-common.c | 9 +++++++-- runtime/uprobes2/uprobes.c | 31 ++++++++++--------------------- tapsets.cxx | 14 ++++++-------- 3 files changed, 23 insertions(+), 31 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2010-10-01 17:58 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=20101001175805.11234.qmail@sourceware.org \ --to=dsmith@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).