public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/106503] "const char []" in local scope never initialized Date: Tue, 02 Aug 2022 07:37:04 +0000 [thread overview] Message-ID: <bug-106503-4-yHnHuCtq4P@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106503-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106503 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- const char junk[] Goes out of scope and you still have a reference to it. -fsanitize=address sometimes can detect this kind of problems at runtime.
next prev parent reply other threads:[~2022-08-02 7:37 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-02 7:31 [Bug c/106503] New: " eb at emlix dot com 2022-08-02 7:36 ` [Bug c/106503] " eb at emlix dot com 2022-08-02 7:37 ` pinskia at gcc dot gnu.org [this message] 2022-08-02 7:47 ` pinskia at gcc dot gnu.org 2022-08-02 9:08 ` eb at emlix dot com 2022-08-02 9:44 ` redi at gcc dot gnu.org 2022-08-02 10:01 ` 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-106503-4-yHnHuCtq4P@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).