public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: fche@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.6-410-gf7719b3 Date: Mon, 14 Nov 2011 14:48:00 -0000 [thread overview] Message-ID: <20111114144830.624.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 f7719b3da58af5eab4872ddf91d9daa4e0b91cff (commit) from 453908cebeeef690013465d5c0872237919d1262 (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 f7719b3da58af5eab4872ddf91d9daa4e0b91cff Author: Frank Ch. Eigler <fche@redhat.com> Date: Mon Nov 14 09:44:52 2011 -0500 PR13313 redux, fix off-by-one error in disp+disp+disp(...) asm operand format commit 8095a157 cleaned up regexp match parsing, but included a bonus off-by-one error that resulted in ignoring the third "disp" optional addend. * tapsets.cxx (sdt_uprobe_var_expanding_visitor::visit_target_symbol_arg) Make optional disp addends count up to three. Four shalt thou not count, neither shalt thou count to two, excepting that thou then proceed to three. Five is right out. ----------------------------------------------------------------------- Summary of changes: tapsets.cxx | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2011-11-14 14:48 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=20111114144830.624.qmail@sourceware.org \ --to=fche@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).