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 analyzer/103233] Warning from system libraries in user code: CWE-476 -Werror=analyzer-null-dereference Date: Mon, 15 Nov 2021 23:42:44 +0000 [thread overview] Message-ID: <bug-103233-4-Wjcd9l7QRV@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 #5 from Alejandro Colomar <colomar.6.4.3 at gmail dot com> --- Is `-fanalyzer` allowed to report errors from system headers exclusively? I mean, ignoring the fact that C++ is unsupported, there's no report at all that relates that error report to my code; not even to libopencv's code. If glibc had a bug, and I compiled a C program that had perfectly defined behavior, would I receive a report for that error?
next prev parent reply other threads:[~2021-11-15 23:42 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 ` [Bug c++/103233] " colomar.6.4.3 at gmail dot com 2021-11-14 14:57 ` 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 [this message] 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-Wjcd9l7QRV@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).