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.8-184-g7bd603e Date: Tue, 14 Aug 2012 01:36:00 -0000 [thread overview] Message-ID: <20120814013647.21755.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 7bd603e17b167affd6c7d2998cee5da699ce5ea5 (commit) from a352456594876f0fc04412b60bff6c2595ace3fb (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 7bd603e17b167affd6c7d2998cee5da699ce5ea5 Author: Josh Stone <jistone@redhat.com> Date: Mon Aug 13 18:32:40 2012 -0700 PR14396: Truncate UTF strings silently The UTF-16 and UTF-32 conversion functions were correctly refusing to write a partial UTF-8 sequence into the buffer, but they were treating that case as an error. It should just silently stop processing, so the result is truncated just as any other string concatenation does. * tapset/linux/conversions.stp (kernel_string_utf32): Treat only rc<0 from _stp_convert_utf32 as an error; rc==0 is truncation. (kernel_string_utf16): Ditto. * tapset/linux/uconversions.stp (user_string_utf32): Ditto. (user_string_utf16): Ditto. * testsuite/systemtap.base/utf_kernel_trunc.*: Test a broad range of truncation points within kernel UTF strings. * testsuite/systemtap.base/utf_user_trunc.*: Same test for userspace. (The duplication is unfortunate, but it's not too crazy.) ----------------------------------------------------------------------- Summary of changes: tapset/linux/conversions.stp | 16 +++-- tapset/linux/uconversions.stp | 16 +++-- testsuite/systemtap.base/utf_kernel_trunc.exp | 30 +++++++++ testsuite/systemtap.base/utf_kernel_trunc.stp | 86 +++++++++++++++++++++++++ testsuite/systemtap.base/utf_user_trunc.c | 74 +++++++++++++++++++++ testsuite/systemtap.base/utf_user_trunc.exp | 45 +++++++++++++ testsuite/systemtap.base/utf_user_trunc.stp | 11 +++ 7 files changed, 266 insertions(+), 12 deletions(-) create mode 100644 testsuite/systemtap.base/utf_kernel_trunc.exp create mode 100644 testsuite/systemtap.base/utf_kernel_trunc.stp create mode 100644 testsuite/systemtap.base/utf_user_trunc.c create mode 100644 testsuite/systemtap.base/utf_user_trunc.exp create mode 100644 testsuite/systemtap.base/utf_user_trunc.stp hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2012-08-14 1:36 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=20120814013647.21755.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).