public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rhialto at falu dot nl" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/103032] false positive diagnostic from -fanalyzer about double-free
Date: Wed, 17 Nov 2021 21:13:00 +0000	[thread overview]
Message-ID: <bug-103032-4-wuQhPdK2jS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103032-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103032

--- Comment #2 from Olaf 'Rhialto' Seibert <rhialto at falu dot nl> ---
I tried my case on a different system with a later gcc version, and it didn't
show the problems I reported. It did however show the diagnostics you showed,
and I think it is correct. strdup() could indeed return NULL.

I don't know how the gcc policy about backporting fixes is. If you don't do it
(and this one isn't super important, just somewhat misleading), then this
report can be closed.

If you might consider a backport, then of course not :)

  parent reply	other threads:[~2021-11-17 21:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-01 21:22 [Bug analyzer/103032] New: " rhialto at falu dot nl
2021-11-16 23:23 ` [Bug analyzer/103032] " dmalcolm at gcc dot gnu.org
2021-11-17 21:13 ` rhialto at falu dot nl [this message]
2021-11-18 15:52 ` dmalcolm 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-103032-4-wuQhPdK2jS@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: link
Be 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).