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-257-g435f53a Date: Tue, 02 Nov 2010 03:13:00 -0000 [thread overview] Message-ID: <20101102031304.5851.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 435f53a7d750fa27c9a73de4716a62c9363b5a91 (commit) from af6a67d0f801ad6dbcbd01d4712cba77f1098adf (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 435f53a7d750fa27c9a73de4716a62c9363b5a91 Author: Frank Ch. Eigler <fche@elastic.org> Date: Mon Nov 1 23:05:56 2010 -0400 fix memory double-free in module_cache The kmodule.stp test case could evoke a double-free of module-info structs, since these were shared pointers, and not managed by GC. Oh yeah, what GC, in the year 2010. * dwflpp.cxx (dwflpp dtor): Don't delete shared mod_info ptr. (module_cache dtor): New function. * dwflpp.h: Declare. * tapsets.cxx (delete_session_module_cache): New function. (several::build_no_more): Call it. (dwarf_build_no_more): Use delete_map<> template. ----------------------------------------------------------------------- Summary of changes: dwflpp.cxx | 10 +++++++++- dwflpp.h | 1 + tapsets.cxx | 43 ++++++++++++++++++++++++------------------- 3 files changed, 34 insertions(+), 20 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2010-11-02 3:13 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=20101102031304.5851.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).