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/109266] Wanalyzer-null-dereference does not warn when struct is at null
Date: Mon, 27 Mar 2023 23:22:16 +0000	[thread overview]
Message-ID: <bug-109266-4-tyP0Etm6EW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109266-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109266

--- Comment #4 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
(In reply to David Malcolm from comment #3)
> (In reply to Jonny Grant from comment #2)
[...]
> > 
> > I wondered if you know how to turn on that "cc1plus: note: source object is
> > likely at address zero? It seems different from normal warnings.
> 
> Grepping the sources shows it's from gcc/pointer-query.cc:
> access_ref::inform_access; I think it's one of the middle-end warnings that
> triggers that, but I'm not sure exactly which (the analyzer doesn't use that
> at the moment).

Grepping for calls to "inform_access" shows that it can come from:
 -Warray_bounds=
 -Wstringop_overflow=
 -Wstringop_overread

  parent reply	other threads:[~2023-03-27 23:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-23 22:17 [Bug analyzer/109266] New: " jg at jguk dot org
2023-03-26 14:58 ` [Bug analyzer/109266] " dmalcolm at gcc dot gnu.org
2023-03-26 21:08 ` jg at jguk dot org
2023-03-27 23:14 ` dmalcolm at gcc dot gnu.org
2023-03-27 23:22 ` dmalcolm at gcc dot gnu.org [this message]
2023-03-31 21:30 ` jg at jguk dot 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-109266-4-tyP0Etm6EW@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).