public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/106140] RFE: analyzer could complain about misuses of socket APIs
Date: Sat, 23 Jul 2022 01:13:08 +0000 [thread overview]
Message-ID: <bug-106140-4-X8iZGzLMur@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106140-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106140
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also|https://gcc.gnu.org/bugzill |
|a/show_bug.cgi?id=106003 |
--- Comment #1 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to David Malcolm from comment #0)
> POSIX has numerous API entrypoints for working with sockets, and,
> presumably, numerous ways of misusing them. They're expressed in terms of
> file-descriptors, and so checking them would interact with PR 106003.
>
Oops wait that's just the analyzer-fd meta-bug; guess I don't need to put it
under "See Also" after all...
next prev parent reply other threads:[~2022-07-23 1:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 22:14 [Bug analyzer/106140] New: " dmalcolm at gcc dot gnu.org
2022-07-23 1:13 ` egallager at gcc dot gnu.org [this message]
2022-10-31 14:15 ` [Bug analyzer/106140] " dmalcolm at gcc dot gnu.org
2022-11-08 3:03 ` dmalcolm at gcc dot gnu.org
2022-11-15 18:59 ` cvs-commit at gcc dot gnu.org
2022-11-15 19:11 ` dmalcolm at gcc dot gnu.org
2022-11-15 19:13 ` dmalcolm at gcc dot gnu.org
2022-11-28 22:20 ` pinskia 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-106140-4-X8iZGzLMur@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).