public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/106776] Unexpected use-after-free warning Date: Tue, 30 Aug 2022 16:34:47 +0000 [thread overview] Message-ID: <bug-106776-4-4KGN60ejY3@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106776-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106776 Martin Sebor <msebor at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |msebor at gcc dot gnu.org --- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> --- Reproduced with the following reduced test case: $ cat pr106776.C && g++ -O2 -S -Wall pr106776.C #include <map> struct matrix_t { int* count; matrix_t() : count(new int(1)) {} matrix_t(const matrix_t& p) : count(p.count) { ++*count; } ~matrix_t() { if (--*count == 0) { delete count; } } }; typedef std::map<int, matrix_t> cache_t; cache_t CACHE; matrix_t* cache(cache_t::iterator lb) { matrix_t wftable; return &CACHE.insert(lb, cache_t::value_type(1, wftable))->second; } In destructor ‘matrix_t::~matrix_t()’, inlined from ‘matrix_t* cache(std::map<int, matrix_t>::iterator)’ at pr106776.C:25:1: pr106776.C:13:23: warning: pointer used after ‘void operator delete(void*, std::size_t)’ [-Wuse-after-free] 13 | ~matrix_t() { if (--*count == 0) { delete count; } } | ^~~~~~ In destructor ‘matrix_t::~matrix_t()’, inlined from ‘std::pair<const int, matrix_t>::~pair()’ at /build/gcc-master/x86_64-pc-linux-gnu/libstdc++-v3/include/bits/stl_pair.h:187:12, inlined from ‘matrix_t* cache(std::map<int, matrix_t>::iterator)’ at pr106776.C:24:37: pr106776.C:13:45: note: call to ‘void operator delete(void*, std::size_t)’ here 13 | ~matrix_t() { if (--*count == 0) { delete count; } } | ^~~~~ The IL in shows the reason for the warning in bb 8 in struct matrix_t * cache (struct iterator lb), seen in the output of -fdump-tree-waccess3: ... <bb 8> [local count: 335388518]: operator delete (_3, 4); <<< _3 deleted pretmp_50 = MEM[(int *)_3]; <<< _3 dereferenced
next prev parent reply other threads:[~2022-08-30 16:34 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-30 9:12 [Bug middle-end/106776] New: " drfiemost at email dot it 2022-08-30 16:34 ` msebor at gcc dot gnu.org [this message] 2022-09-28 14:33 ` [Bug middle-end/106776] " drfiemost at email dot it 2022-10-22 1:08 ` pinskia at gcc dot gnu.org 2022-10-22 1:24 ` pinskia at gcc dot gnu.org 2022-10-22 1:27 ` pinskia at gcc dot gnu.org 2023-05-30 17:03 ` drfiemost at yahoo dot com
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-106776-4-4KGN60ejY3@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).