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.0-516-g19d91f6
Date: Fri, 15 Jan 2010 00:46:00 -0000	[thread overview]
Message-ID: <20100115004651.28264.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  19d91f6c2fcc4dea3b86e05721275cf0f8117e74 (commit)
      from  622fa74aa720b3eda55c81530d458e3ea7792bb2 (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 19d91f6c2fcc4dea3b86e05721275cf0f8117e74
Author: Josh Stone <jistone@redhat.com>
Date:   Thu Jan 14 16:40:45 2010 -0800

    PR11151: Recover stap_uprobes slots on process exit
    
    When a process exits, it won't necessarily bother to munmap all of its
    shared libraries.  This patch makes sure that with uprobes in libraries,
    we still grab an exit notification and clear everything out.
    
    * runtime/uprobes-common.c (stap_uprobe_process_munmap): New.
    * tapsets.cxx (uprobe_derived_probe_group::emit_module_decls): Use above
      callback so that we can recover our resources on process exit.

-----------------------------------------------------------------------

Summary of changes:
 runtime/uprobes-common.c |   15 +++++++++++++++
 runtime/uprobes-common.h |    1 +
 tapsets.cxx              |    1 +
 3 files changed, 17 insertions(+), 0 deletions(-)


hooks/post-receive
--
systemtap: system-wide probe/trace tool


                 reply	other threads:[~2010-01-15  0:46 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=20100115004651.28264.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: link
Be 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).