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.3-237-ge789965 Date: Wed, 27 Oct 2010 19:36:00 -0000 [thread overview] Message-ID: <20101027193657.15006.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 e789965751d7f6dac4d5e7cdce71586595bfc572 (commit) from e5a24d28d4cfac54046375978b3784b0e5bdce8a (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 e789965751d7f6dac4d5e7cdce71586595bfc572 Author: Frank Ch. Eigler <fche@elastic.org> Date: Wed Oct 27 15:35:10 2010 -0400 valgrind cleanups: memory leaks, uninit variable warnings * dwflpp.cxx (dwflpp dtor): delete mod_info. (express_as_string): Don't preallocate memory for open_memstream. (literal_stmt_for_*): Fully free obstack after loc2c work. * hash.cxx (add_file): Clear out struct stat before hashing. * translate.cxx (dump_unwindsyms): Free eh/debug_frame_hdr at end. ----------------------------------------------------------------------- Summary of changes: dwflpp.cxx | 19 ++++++++++++------- hash.cxx | 1 + translate.cxx | 4 ++++ 3 files changed, 17 insertions(+), 7 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2010-10-27 19:36 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=20101027193657.15006.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).