public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: cmeek@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.7-285-g985892d
Date: Wed, 06 Jun 2012 15:48:00 -0000	[thread overview]
Message-ID: <20120606154825.29290.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  985892de26421af1689dc6ecdfde9cc74208548c (commit)
       via  891043f0a71cf62a873f0b134f788fb94fe39a66 (commit)
       via  b96901b711b418ce0a8e74351223760a65e32c42 (commit)
      from  aa1b093fc154a5e7b13f08ef752e486ffba987f9 (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 985892de26421af1689dc6ecdfde9cc74208548c
Author: Chris Meek <cmeek@redhat.com>
Date:   Wed Jun 6 11:43:59 2012 -0400

    PR13516: More robust handling of crtl-c
    
    Rather than return or break after checking if(pending_inturrupts),
    we now throw an interrupt_exception. This is caught in main, where
    we immediately exit.
    
    Also added some code to check for other uncaght exceptions.

commit 891043f0a71cf62a873f0b134f788fb94fe39a66
Author: Chris Meek <cmeek@redhat.com>
Date:   Mon Jun 4 16:10:16 2012 -0400

    PR13516: Shifted main (style cleanup)
    
      Shifted main right by one tab to align properly with
      the new try/catch block. Decided to do this in a separate commit
      so as to make the previous one more clear.

commit b96901b711b418ce0a8e74351223760a65e32c42
Author: Chris Meek <cmeek@redhat.com>
Date:   Mon Jun 4 16:00:50 2012 -0400

    PR13516 pre: Re-worked tmpdir creation/removal
    
    In preparation for PR13516, we needed to rework the tmpdir
    creation/removal, so as to be sure the tmpdir gets removed
    when we get an exception. Creation now happens in the
    systemtap_session ctor with a call to
    systemtap_session::create_tmp_dir() and removal in the dtor
    with a call to systemtap_session::remove_tmp_dir().
    
    passes_0_4_again_with_server() now calls the new
    systemtap_session::reset_tmp_dir(), rather than just removing
    and relying on passes_0_4() to recreate it.

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

Summary of changes:
 buildrun.cxx  |    3 +-
 csclient.cxx  |   15 ++-
 dwflpp.cxx    |   16 ++-
 elaborate.cxx |   26 ++--
 main.cxx      |  370 +++++++++++++++++++++++++--------------------------------
 session.cxx   |   62 ++++++++++
 session.h     |   14 ++
 setupdwfl.cxx |    6 +-
 tapsets.cxx   |    4 +-
 translate.cxx |   14 +-
 10 files changed, 285 insertions(+), 245 deletions(-)


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


                 reply	other threads:[~2012-06-06 15:48 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=20120606154825.29290.qmail@sourceware.org \
    --to=cmeek@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).