public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: cmeek@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.8-38-g3f803f9 Date: Thu, 12 Jul 2012 14:31:00 -0000 [thread overview] Message-ID: <20120712143153.9827.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 3f803f9ee09362f0e77812859d43448e477780f5 (commit) from cdc9594b4fead7d90c8dd641118f4ae8854764f4 (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 3f803f9ee09362f0e77812859d43448e477780f5 Author: Chris Meek <cmeek@redhat.com> Date: Thu Jul 12 10:14:48 2012 -0400 BZ802380: Fixed logic issue and resource leak - Coverity Coverity issues caught: REVERSE_INULL There were some logic issues in sdt_query::setup_note_probe_entry() with a check for whether "name" was NULL after it was dereferenced, as well as copying a couple possibly not '\0' terminated char *'s to strings. These should now be fixed, and work as intended. RESOURCE_LEAK Also, there was a resource leak with ai_tvar_base in dwarf_var_expanding_visitor::gen_mapped_saved_return(). That should now also be fixed. ----------------------------------------------------------------------- Summary of changes: tapsets.cxx | 22 ++++++++++++---------- 1 files changed, 12 insertions(+), 10 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2012-07-12 14:31 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=20120712143153.9827.qmail@sourceware.org \ --to=cmeek@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).