public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/65434] Memory leak in pool constructor Date: Mon, 16 Mar 2015 16:00:00 -0000 [thread overview] Message-ID: <bug-65434-4-MyxF7Caroe@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65434-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65434 --- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to Dmitry Shachnev from comment #2) > Will anything bad happen if that memory is freed in the destructor? Yes, because other destructors could run later, and could (potentially) need to use the pool after it had been destroyed. That would be undefined behaviour. > For me, the issue is mostly aesthetic — I got used to not seeing any > Valgrind warnings in my programs :) Then add a valgrind suppression, or ask upstream valgrind to add it. >From gcc-bugs-return-480476-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 16 16:10:53 2015 Return-Path: <gcc-bugs-return-480476-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 115734 invoked by alias); 16 Mar 2015 16:10:53 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: <gcc-bugs.gcc.gnu.org> List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/> List-Post: <mailto:gcc-bugs@gcc.gnu.org> List-Help: <mailto:gcc-bugs-help@gcc.gnu.org> Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 115674 invoked by uid 55); 16 Mar 2015 16:10:49 -0000 From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/65431] [5 Regression] Invalid read of size 8 at 0x105DBBF8: delete_omp_context(unsigned long) (omp-low.c:1586) Date: Mon, 16 Mar 2015 16:10:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 5.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jakub at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org X-Bugzilla-Target-Milestone: 5.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: <bug-65431-4-W8xt3XsYx9@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-65431-4@http.gcc.gnu.org/bugzilla/> References: <bug-65431-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-03/txt/msg01620.txt.bz2 Content-length: 519 https://gcc.gnu.org/bugzilla/show_bug.cgi?ide431 --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Author: jakub Date: Mon Mar 16 16:10:17 2015 New Revision: 221459 URL: https://gcc.gnu.org/viewcvs?rev"1459&root=gcc&view=rev Log: PR middle-end/65431 * omp-low.c (delete_omp_context): Only splay_tree_delete reduction_map in GIMPLE_OMP_TARGET is_gimple_omp_offloaded is_gimple_omp_oacc contexts. Don't look at ctx->outer. Modified: trunk/gcc/ChangeLog trunk/gcc/omp-low.c
prev parent reply other threads:[~2015-03-16 16:00 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-03-16 11:03 [Bug libstdc++/65434] New: " mitya57 at gmail dot com 2015-03-16 15:09 ` [Bug libstdc++/65434] " redi at gcc dot gnu.org 2015-03-16 15:33 ` mitya57 at gmail dot com 2015-03-16 16:00 ` redi at gcc dot gnu.org [this message]
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=bug-65434-4-MyxF7Caroe@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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).