public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug analyzer/99193] Bogus "should have been deallocated with 'free' but was deallocated with 'realloc' [CWE-762] [-Werror=analyzer-mismatching-deallocation]" Date: Thu, 25 Feb 2021 14:27:15 +0000 [thread overview] Message-ID: <bug-99193-4-aEva7CLd2p@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99193-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99193 --- Comment #11 from David Malcolm <dmalcolm at gcc dot gnu.org> --- BTW, looking at the #pragma GCC diagnostic ignored "-Wanalyzer-null-argument" at https://github.com/libguestfs/libguestfs/blob/f19fd566f6387ce7e4d82409528c9dde374d25e0/df/main.c#L317 I'm guessing that this was due to PR analyzer/99196, due to the: name = strdup (drvs->uri.orig_uri); if (name == NULL) error (EXIT_FAILURE, errno, "strdup"); p = strrchr (name, '/'); where the analyzer didn't "know" that the error call would terminate the program; so hopefully this is also fixed now.
next prev parent reply other threads:[~2021-02-25 14:27 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-22 10:01 [Bug c/99193] New: " rjones at redhat dot com 2021-02-22 10:05 ` [Bug c/99193] " rjones at redhat dot com 2021-02-22 10:13 ` rjones at redhat dot com 2021-02-22 10:14 ` rjones at redhat dot com 2021-02-22 10:36 ` rjones at redhat dot com 2021-02-22 15:21 ` [Bug analyzer/99193] " msebor at gcc dot gnu.org 2021-02-22 22:27 ` dmalcolm at gcc dot gnu.org 2021-02-24 21:03 ` dmalcolm at gcc dot gnu.org 2021-02-25 0:57 ` cvs-commit at gcc dot gnu.org 2021-02-25 0:59 ` dmalcolm at gcc dot gnu.org 2021-02-25 11:20 ` rjones at redhat dot com 2021-02-25 14:27 ` dmalcolm at gcc dot gnu.org [this message] 2021-02-25 14:41 ` rjones at redhat 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-99193-4-aEva7CLd2p@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).