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.1-86-gd9f5825 Date: Wed, 17 Feb 2010 02:11:00 -0000 [thread overview] Message-ID: <20100217021152.14980.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 d9f58253e30ea80e57d8f54e41e9cd114cc13973 (commit) via 4fa8e6497405fd4f121a3eee0c6d772aaeeef6d8 (commit) via 2a818a16b0c371977303e464bfc75ad8814a9c7a (commit) from e6364d7923d49c7bfe1a807cd877cb9b29ca0acf (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 d9f58253e30ea80e57d8f54e41e9cd114cc13973 Author: Josh Stone <jistone@redhat.com> Date: Mon Feb 15 21:27:37 2010 -0800 Use clamping to more easily normalize input values The kernel has min/max/clamp macros to make range comparisons easier. Clamp is a newer invention, but we can define it for older kernels in terms of min and max. commit 4fa8e6497405fd4f121a3eee0c6d772aaeeef6d8 Author: Josh Stone <jistone@redhat.com> Date: Mon Feb 15 21:21:02 2010 -0800 PR11282: Keep the md4 state in the hash copy constructor We were getting new hash collisions, because the new hash copy constructor was restarting the md4 computation. Everything from get_base_hash was thus lost. * hash.h (hash::hash): Keep the md4 state when copying. commit 2a818a16b0c371977303e464bfc75ad8814a9c7a Author: Josh Stone <jistone@redhat.com> Date: Mon Feb 15 19:28:43 2010 -0800 PR11277: Use consistent octal in quoted strings Previously, our octal escapes used variable lengths, which can lead to ambiguities. Also, 8-bit characters would only output the least digit. * runtime/string.c (_stp_text_str): Always output 3-digit octal escapes, and handle 8-bit chars more gracefully. * testsuite/systemtap.string/text_str.stp: Include an 8-bit character. * testsuite/systemtap.string/text_str.exp: Above + expect 3-digit octal. ----------------------------------------------------------------------- Summary of changes: hash.h | 2 +- runtime/runtime.h | 8 +++++++ runtime/string.c | 17 ++++---------- runtime/vsprintf.c | 12 +++++----- tapset/conversions.stp | 12 +++------- tapset/string.stp | 9 ++++--- testsuite/systemtap.string/text_str.exp | 36 +++++++++++++++--------------- testsuite/systemtap.string/text_str.stp | 10 ++++---- 8 files changed, 52 insertions(+), 54 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2010-02-17 2:11 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=20100217021152.14980.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).