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/110830] -Wanalyzer-use-of-uninitialized-value false negative due to use-after-free::supercedes_p. Date: Mon, 31 Jul 2023 22:43:29 +0000 [thread overview] Message-ID: <bug-110830-4-IQorX3DZ5P@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110830-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110830 --- Comment #2 from David Malcolm <dmalcolm at gcc dot gnu.org> --- The "supercedes_p" logic is called in diagnostic_manager::emit_saved_diagnostics here: best_candidates.handle_interactions (this); I *think* every saved_diagnostic ought to have a non-NULL m_best_epath by the time this is called.
next prev parent reply other threads:[~2023-07-31 22:43 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-27 12:41 [Bug analyzer/110830] New: " vultkayn at gcc dot gnu.org 2023-07-31 22:40 ` [Bug analyzer/110830] " dmalcolm at gcc dot gnu.org 2023-07-31 22:43 ` dmalcolm at gcc dot gnu.org [this message] 2023-09-07 21:02 ` 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-110830-4-IQorX3DZ5P@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).