public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: mark@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.8-225-g6c779e6 Date: Mon, 10 Sep 2012 08:32:00 -0000 [thread overview] Message-ID: <20120910083240.18792.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 6c779e63fd87d9ac609d33218ac58cbb31f43648 (commit) from fa696039448ed6a6f72c6ecac8e7e664820cbf6e (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 6c779e63fd87d9ac609d33218ac58cbb31f43648 Author: Mark Wielaard <mjw@redhat.com> Date: Mon Sep 10 10:29:15 2012 +0200 dflpp.cxx (find_variable_and_frame_base): Remove extra bracket in error. Before: semantic error: unable to find local 'task', dieoffset 0x111604 in nfs, near pc 0x78863 in nfs_read_done fs/nfs/proc.c ( (alternatives: $data): identifier '$task' at [...] After: semantic error: unable to find local 'task', dieoffset 0x111604 in nfs, near pc 0x78863 in nfs_read_done fs/nfs/proc.c (alternatives: $data): identifier '$task' at [...] ----------------------------------------------------------------------- Summary of changes: dwflpp.cxx | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2012-09-10 8:32 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=20120910083240.18792.qmail@sourceware.org \ --to=mark@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).