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/98989] New: missing -Wfree-nonheap-object freeing std::strings over 15 bytes long Date: Sun, 07 Feb 2021 22:23:35 +0000 [thread overview] Message-ID: <bug-98989-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98989 Bug ID: 98989 Summary: missing -Wfree-nonheap-object freeing std::strings over 15 bytes long Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: msebor at gcc dot gnu.org Target Milestone: --- Given the test case below, -Wfree-nonheap-object detects the invalid attempt to free the std::string buffer provided the string constant it's initialized with is no more than 15 characters long (plus the terminating nul). But the option fails to diagnose the invalid call once the string length is 16 or more. #include <string> void f () { std::string str (STR); char *p = &str[0]; free (p); } $ g++ -DSTR='"abcdefghijklmno"' -O2 -S -Wall t.C t.C: In function ‘void f()’: t.C:7:8: warning: ‘void free(void*)’ called on unallocated object ‘str’ [-Wfree-nonheap-object] 7 | free (p); | ~~~~~^~~ t.C:5:15: note: declared here 5 | std::string str (STR); | ^~~
next reply other threads:[~2021-02-07 22:23 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-07 22:23 msebor at gcc dot gnu.org [this message] 2021-02-07 22:44 ` [Bug middle-end/98989] " msebor at gcc dot gnu.org 2021-02-07 22:59 ` msebor at gcc dot gnu.org 2021-02-07 23:22 ` msebor at gcc dot gnu.org
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-98989-4@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).