public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "colomar.6.4.3 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/103233] Warning from system libraries in user code: CWE-476 -Werror=analyzer-null-dereference
Date: Sun, 14 Nov 2021 14:30:00 +0000 [thread overview]
Message-ID: <bug-103233-4-KuhhYStWy6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103233-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103233
--- Comment #1 from Alejandro Colomar <colomar.6.4.3 at gmail dot com> ---
$ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux bookworm/sid"
NAME="Debian GNU/Linux"
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
$ dpkg -l "*[cg]++*"
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-=========================-============-============-===============================================
un c++-compiler <none> <none> (no description
available)
un c++abi2-dev <none> <none> (no description
available)
ii g++ 4:11.2.0-2 amd64 GNU C++ compiler
ii g++-11 11.2.0-10 amd64 GNU C++ compiler
un g++-11-multilib <none> <none> (no description
available)
un g++-multilib <none> <none> (no description
available)
un g++-x86-64-linux-gnu <none> <none> (no description
available)
ii lib32stdc++6 11.2.0-10 amd64 GNU Standard C++
Library v3 (32 bit Version)
un libg++2.8-dev <none> <none> (no description
available)
un libg++27-dev <none> <none> (no description
available)
un libg++272-dev <none> <none> (no description
available)
un libsigc++-2.0-0c2a <none> <none> (no description
available)
ii libsigc++-2.0-0v5:amd64 2.10.4-2 amd64 type-safe Signal
Framework for C++ - runtime
ii libstdc++-10-dev:amd64 10.3.0-12 amd64 GNU Standard C++
Library v3 (development files)
un libstdc++-10-doc <none> <none> (no description
available)
ii libstdc++-11-dev:amd64 11.2.0-10 amd64 GNU Standard C++
Library v3 (development files)
un libstdc++-11-doc <none> <none> (no description
available)
un libstdc++-dev <none> <none> (no description
available)
un libstdc++2.10-dev <none> <none> (no description
available)
un libstdc++2.8-dev <none> <none> (no description
available)
un libstdc++2.9-dev <none> <none> (no description
available)
un libstdc++2.9-glibc2.1-dev <none> <none> (no description
available)
un libstdc++3.0-dev <none> <none> (no description
available)
ii libstdc++6:amd64 11.2.0-10 amd64 GNU Standard C++
Library v3
un libstdc++6-11-dbg <none> <none> (no description
available)
next prev parent reply other threads:[~2021-11-14 14:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-14 14:27 [Bug c++/103233] New: " colomar.6.4.3 at gmail dot com
2021-11-14 14:30 ` colomar.6.4.3 at gmail dot com [this message]
2021-11-14 14:57 ` [Bug c++/103233] " redi at gcc dot gnu.org
2021-11-14 15:32 ` [Bug analyzer/103233] " alx.manpages at gmail dot com
2021-11-15 23:27 ` dmalcolm at gcc dot gnu.org
2021-11-15 23:42 ` colomar.6.4.3 at gmail dot com
2021-11-15 23:48 ` colomar.6.4.3 at gmail dot com
2021-11-15 23:52 ` pinskia at gcc dot gnu.org
2021-11-16 11:32 ` alx.manpages at gmail dot com
2021-12-13 15:45 ` redi 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-103233-4-KuhhYStWy6@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).