public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "geoffreydgr at icloud dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug analyzer/109106] New: GCC Static Analyzer doesn't model printf Date: Sun, 12 Mar 2023 13:08:09 +0000 [thread overview] Message-ID: <bug-109106-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109106 Bug ID: 109106 Summary: GCC Static Analyzer doesn't model printf Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: analyzer Assignee: dmalcolm at gcc dot gnu.org Reporter: geoffreydgr at icloud dot com Target Milestone: --- GCC Static Analyzer does not model `printf`. see it live: https://godbolt.org/z/6ooW44sPq Input: ```c #include <stdio.h> int main() { int *j = 0; printf("NPD_FLAG\n") || *j; } ``` Output: ``` <source>: In function 'main': <source>:10:27: warning: dereference of NULL 'j' [CWE-476] [-Wanalyzer-null-dereference] 10 | printf("NPD_FLAG\n") || *j; | ^~ 'main': events 1-4 | | 9 | int *j = 0; | | ^ | | | | | (1) 'j' is NULL | 10 | printf("NPD_FLAG\n") || *j; | | ~~~~~~~~~~~~~~~~~~~~~~~~~~ | | | | | | | (3) ...to here | | | (4) dereference of NULL 'j' | | (2) following 'false' branch... | Compiler returned: 0 ```
next reply other threads:[~2023-03-12 13:08 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-12 13:08 geoffreydgr at icloud dot com [this message] 2023-03-12 14:35 ` [Bug analyzer/109106] " pinskia at gcc dot gnu.org 2023-03-12 19:40 ` pinskia at gcc dot gnu.org 2023-03-12 20:19 ` schwab@linux-m68k.org 2023-03-13 14:20 ` dmalcolm at gcc dot gnu.org 2023-07-19 17:11 ` geoffreydgr at icloud dot com
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-109106-4@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).