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/114677] [13/14 Regression] -Wanalyzer-fd-leak false positive writing to int * param
Date: Wed, 10 Apr 2024 16:49:44 +0000 [thread overview]
Message-ID: <bug-114677-4-JrMTWzWWg8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114677-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114677
David Malcolm <dmalcolm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2024-04-10
Summary|apparent -Wanalyzer-fd-leak |[13/14 Regression]
| false positive |-Wanalyzer-fd-leak false
| |positive writing to int *
| |param
Ever confirmed|0 |1
--- Comment #1 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Thanks for filing this bug.
Confirmed (thanks for the godbolt link).
Affects GCC 13 onwards (which added that warning)
Looks like for some reason the analyzer isn't treating (*sock) as keeping the
value of the fd alive.
next prev parent reply other threads:[~2024-04-10 16:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 13:24 [Bug analyzer/114677] New: apparent -Wanalyzer-fd-leak false positive levon at movementarian dot org
2024-04-10 16:49 ` dmalcolm at gcc dot gnu.org [this message]
2024-04-14 5:23 ` [Bug analyzer/114677] [13/14 Regression] -Wanalyzer-fd-leak false positive writing to int * param pinskia at gcc dot gnu.org
2024-04-17 13:34 ` law at gcc dot gnu.org
2024-05-21 9:19 ` [Bug analyzer/114677] [13/14/15 " jakub 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-114677-4-JrMTWzWWg8@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).