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-470-gba316a5
Date: Mon, 12 Jul 2010 20:20:00 -0000	[thread overview]
Message-ID: <20100712202046.9628.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  ba316a59c2efe957635ff6702ffcae4526187e2d (commit)
      from  6e9c532dd5b5ed64c6ba2e5d919e81ad03333abe (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 ba316a59c2efe957635ff6702ffcae4526187e2d
Author: Josh Stone <jistone@redhat.com>
Date:   Mon Jul 12 13:01:51 2010 -0700

    Add all the weirdness to compat-%p
    
    I thought the old %p behavior was as simple as %#.8x or %#.16x, but it
    was even weirder than that, as the ptr.exp test reveals.  The compat
    path is now able to pass that test, and a new test makes sure of the new
    code behaves as expected too.
    
    * runtime/vsprintf.c (_stp_vsnprintf): compat-%p is better preserved.
    * testsuite/systemtap.printf/ptr.exp -> ptr-1.2.exp: Keep as a compat
      test, and add a check that %.Np precision is ignored.
    * testsuite/systemtap.printf/ptr-1.3.exp: New, make sure that %p really
      does act like %#x now, with various field_width.precision combos.

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

Summary of changes:
 runtime/vsprintf.c                                 |   42 +++++++--
 .../systemtap.printf/{ptr.exp => ptr-1.2.exp}      |   20 ++++-
 .../systemtap.printf/{ptr.stp => ptr-1.2.stp}      |    8 ++
 testsuite/systemtap.printf/ptr-1.3.exp             |   69 +++++++++++++++
 testsuite/systemtap.printf/ptr-1.3.stp             |   90 ++++++++++++++++++++
 5 files changed, 215 insertions(+), 14 deletions(-)
 rename testsuite/systemtap.printf/{ptr.exp => ptr-1.2.exp} (78%)
 rename testsuite/systemtap.printf/{ptr.stp => ptr-1.2.stp} (83%)
 create mode 100644 testsuite/systemtap.printf/ptr-1.3.exp
 create mode 100644 testsuite/systemtap.printf/ptr-1.3.stp


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


                 reply	other threads:[~2010-07-12 20:20 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=20100712202046.9628.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).