public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: fche@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.6-388-ga06c6bd
Date: Mon, 07 Nov 2011 19:23:00 -0000	[thread overview]
Message-ID: <20111107192327.17635.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  a06c6bd3c6a7ea89f6387c4a29d977b95865a12c (commit)
       via  c114ce7ffcb39e37f6468be80ffa3fa1f18bcf0e (commit)
       via  fcf41197e6e1500b60aba1c838e2d9fe53e2c98a (commit)
      from  3780aaa7c3ddd4af58adcb24c186af0738340935 (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 a06c6bd3c6a7ea89f6387c4a29d977b95865a12c
Author: Frank Ch. Eigler <fche@redhat.com>
Date:   Mon Nov 7 14:20:26 2011 -0500

    PR13386: avoid _stp_printf() crash for null context / %M or %m
    
    If _stp_printf() were invoked with %M or %m directive that resulted in
    an error, it likes to write into the current stap probe handler
    context about it.  However, _stp_printf is sometimes used outside
    probe handler context, in which case no context is actually available,
    such as during module_exit().  So we tolerate a null context pointer
    (it just having been deallocated).  Note that there don't exist any
    current %M/%m outputs in the runtime that could trigger this
    NULL-deref, so this is only a prophylactic measure.
    
    * runtime/vsprintf.c (_stp_vsprint_memory): Tolerate null context.

commit c114ce7ffcb39e37f6468be80ffa3fa1f18bcf0e
Author: Frank Ch. Eigler <fche@redhat.com>
Date:   Mon Nov 7 14:19:05 2011 -0500

    PR13386: disable preemption around printing-happy parts of *module_exit().
    
    * translate.cxx (c_unparser::emit_module_exit): Since we use stp_printf
      (that internally is preempt-sensitive), we need to disable preemption
      (or at least cpu switching) during this stage.

commit fcf41197e6e1500b60aba1c838e2d9fe53e2c98a
Author: Frank Ch. Eigler <fche@redhat.com>
Date:   Mon Nov 7 14:18:44 2011 -0500

    PR13338: make test case pass even without coreutils-debuginfo

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

Summary of changes:
 runtime/vsprintf.c                   |    6 ++++--
 testsuite/systemtap.base/bz13338.exp |    4 ++++
 translate.cxx                        |   10 ++++++++++
 3 files changed, 18 insertions(+), 2 deletions(-)


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


                 reply	other threads:[~2011-11-07 19:23 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=20111107192327.17635.qmail@sourceware.org \
    --to=fche@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).