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.2-486-g52f3db8
Date: Tue, 13 Jul 2010 18:58:00 -0000	[thread overview]
Message-ID: <20100713185857.23386.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  52f3db8580c099404083b39160334489dd6ed288 (commit)
       via  c55ea10d8fae0dae36d0428d7bc49ef0131300f1 (commit)
      from  fd20a70c5b0947045d9fbbd59dc2e12f58f2e200 (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 52f3db8580c099404083b39160334489dd6ed288
Author: Josh Stone <jistone@redhat.com>
Date:   Tue Jul 13 11:10:32 2010 -0700

    Add tests for PR11808 and PR11809
    
    * testsuite/semok/pr11808.stp: Make sure we don't abort().
    * testsuite/semok/pr11809.stp: Make sure we don't underflow.

commit c55ea10d8fae0dae36d0428d7bc49ef0131300f1
Author: Josh Stone <jistone@redhat.com>
Date:   Tue Jul 13 10:25:48 2010 -0700

    Allow pretty-printing with partial availability
    
    Especially with local structs, DWARF may only have parts of a variable
    available at runtime.  This change lets us print '?' for inaccessible
    parts, so we can still print the parts we do have.
    
    * tapsets.cxx (dwarf_pretty_print::push_deref): New, try a deref and
      push a '?' instead if it fails.
      (dwarf_pretty_print::recurse): Use push_deref instead of deref.
      (dwarf_pretty_print::recurse_base): Ditto.
      (dwarf_pretty_print::recurse_pointer): Ditto.
      (dwarf_pretty_print::print_chars): Ditto.

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

Summary of changes:
 tapsets.cxx                 |   60 ++++++++++++++++++++++++++++---------------
 testsuite/semok/pr11808.stp |    7 +++++
 testsuite/semok/pr11809.stp |    8 +++++
 3 files changed, 54 insertions(+), 21 deletions(-)
 create mode 100755 testsuite/semok/pr11808.stp
 create mode 100755 testsuite/semok/pr11809.stp


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


                 reply	other threads:[~2010-07-13 18: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=20100713185857.23386.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).