public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: dsmith@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.7-215-gb0f614a Date: Tue, 08 May 2012 21:07:00 -0000 [thread overview] Message-ID: <20120508210738.29371.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 b0f614a0087883d359f3376f32bd62dc06907bb0 (commit) from 5b2bc70bd7db920c50b90cea554ca93a02cdf0b2 (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 b0f614a0087883d359f3376f32bd62dc06907bb0 Author: David Smith <dsmith@redhat.com> Date: Tue May 8 16:07:08 2012 -0500 Give good error messages for inodes uprobes registration errors. * translate.cxx (c_unparser::emit_module_init): Only print an error if 'probe_point' isn't NULL. * tapsets.cxx (uprobe_derived_probe_group::emit_module_inode_init): Let stapiu_init() handle reporting errors by setting 'probe_point' to NULL. * runtime/uprobes-inode.c (stapiu_get): Print errors when needed. (stapiu_reg): Ditto. ----------------------------------------------------------------------- Summary of changes: runtime/uprobes-inode.c | 30 ++++++++++++++++++++++-------- tapsets.cxx | 3 +++ translate.cxx | 4 ++++ 3 files changed, 29 insertions(+), 8 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2012-05-08 21:07 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=20120508210738.29371.qmail@sourceware.org \ --to=dsmith@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).