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.6-283-gc50772a Date: Fri, 07 Oct 2011 17:16:00 -0000 [thread overview] Message-ID: <20111007171634.7088.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 c50772a9b5c9ca7c18e18bc747ae03d1f33adf24 (commit) via 1386d8fc1a768df68e830e4af8482cdf060612a1 (commit) from 898000ace6a5a03ffb7a129b8291cf7f58c4fb26 (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 c50772a9b5c9ca7c18e18bc747ae03d1f33adf24 Author: Josh Stone <jistone@redhat.com> Date: Fri Oct 7 10:13:38 2011 -0700 PR3217: Fix systemtap.base/vars.exp This test has a grep on pass-3 code, which started matching too much with the new compiled-printf output. This tightens that grep down a bit, and adds a comment explaining what the test is trying to do. commit 1386d8fc1a768df68e830e4af8482cdf060612a1 Author: Josh Stone <jistone@redhat.com> Date: Fri Oct 7 09:48:43 2011 -0700 PR13272: Fix quoted strings in the printf shortcut path For printf strings with no arguments, we usually skip all the printf path altogether and just use _stp_print. However, the compiled-printf changes affected the level of string escaping, which broke for a case like printf("\"quote\\this\"\n"). We must make sure that this shortcut path uses an output-quoted string literal. * translate.cxx (c_unparser::visit_print_format): Generate an output- quoted format_string too, for use by the _stp_print shortcut. (preprocess_print_format): The "%s\n" case shouldn't alter components. * testsuite/buildok/printf.stp: Add "%s" and "%s\n" shortcut tests too. ----------------------------------------------------------------------- Summary of changes: testsuite/buildok/printf.stp | 2 ++ testsuite/systemtap.base/vars.exp | 10 +++++++++- translate.cxx | 10 +++++----- 3 files changed, 16 insertions(+), 6 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2011-10-07 17:16 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=20111007171634.7088.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: linkBe 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).