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.7-173-g941101c Date: Fri, 20 Apr 2012 00:27:00 -0000 [thread overview] Message-ID: <20120420002739.23130.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 941101c14c98c0b9ee186d894382bce082f5c16f (commit) via 5650ca76f837f174335741915c63091912da9e0c (commit) from 600551ca9fb694d2757d66a4bf281dcf6934d9bf (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 941101c14c98c0b9ee186d894382bce082f5c16f Author: Josh Stone <jistone@redhat.com> Date: Thu Apr 19 17:19:53 2012 -0700 PR13999: Use %#c to escape pretty-printed characters We especially need escaping to combat \0 characters, which would truncate the rest of the pretty-printed string. * tapsets.cxx (dwarf_pretty_print::recurse_base): Use %#c for chars. * testsuite/systemtap.printf/pretty-char.*: Test char escaping. commit 5650ca76f837f174335741915c63091912da9e0c Author: Josh Stone <jistone@redhat.com> Date: Thu Apr 19 17:11:14 2012 -0700 PR13999: Let "%#c" add escapes for nonprintables The special '#' flag previously didn't do anything for characters. Now it signals that non-printable characters should be escaped in the output string, either using C shortcuts or octal values. * runtime/vsprintf.c (_stp_vsprint_char_size, _stp_vsprint_char): New functions to size and fill the buffer, accounting for escape chars. (_stp_vsnprintf): Use the new char functions. * translate.cxx (c_unparser::emit_compiled_printfs): Ditto. * testsuite/systemtap.printf/char2.*: Test %#c * NEWS, stap.1: Document it. ----------------------------------------------------------------------- Summary of changes: NEWS | 2 + runtime/vsprintf.c | 153 +++++++++++++++++--- runtime/vsprintf.h | 4 + stap.1 | 10 ++ tapsets.cxx | 4 +- testsuite/systemtap.printf/char2.exp | 7 + testsuite/systemtap.printf/char2.stp | 17 +++ .../{pretty-bits.exp => pretty-char.exp} | 4 +- testsuite/systemtap.printf/pretty-char.h | 1 + testsuite/systemtap.printf/pretty-char.stp | 16 ++ translate.cxx | 12 +- 11 files changed, 195 insertions(+), 35 deletions(-) create mode 100644 testsuite/systemtap.printf/char2.exp create mode 100644 testsuite/systemtap.printf/char2.stp copy testsuite/systemtap.printf/{pretty-bits.exp => pretty-char.exp} (63%) create mode 100644 testsuite/systemtap.printf/pretty-char.h create mode 100644 testsuite/systemtap.printf/pretty-char.stp hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2012-04-20 0:27 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=20120420002739.23130.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).