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/99771] New: Analyzer diagnostics should not say "<unknown>"
Date: Thu, 25 Mar 2021 15:26:15 +0000	[thread overview]
Message-ID: <bug-99771-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 99771
           Summary: Analyzer diagnostics should not say "<unknown>"
           Product: gcc
           Version: 11.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: analyzer
          Assignee: dmalcolm at gcc dot gnu.org
          Reporter: dmalcolm at gcc dot gnu.org
  Target Milestone: ---

Various analyzer diagnostics talk about "<unknown>"; examples can be seen in
the testsuite:
  data-model-10.c:
    *new_table->m_f = NULL; // "dereference of possibly-NULL '<unknown>'"

  malloc-1.c (test_44):
    free (global_ptr); // "leak of '<unknown>'"

  malloc-ipa-13.c:
    calls_free (f.m_p); //"passing freed pointer '<unknown>' in call to
'calls_free' from 'test'"

and IIRC I've seen these "in the wild" recently as well.

We shouldn't emit "<unknown>" to the end-user.

Filing this bug to have a place to track fixing these.

             reply	other threads:[~2021-03-25 15:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-25 15:26 dmalcolm at gcc dot gnu.org [this message]
2021-03-25 15:26 ` [Bug analyzer/99771] " dmalcolm at gcc dot gnu.org
2021-03-30 21:52 ` cvs-commit at gcc dot gnu.org
2021-03-31 23:18 ` cvs-commit at gcc dot gnu.org
2021-03-31 23:21 ` dmalcolm at gcc dot gnu.org
2022-03-07 19:21 ` cvs-commit at gcc dot gnu.org
2022-03-08 19:17 ` cvs-commit 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-99771-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: 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).