public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jacob.benoit.1 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/63272] New: GCC should warn when using pointer to dead scoped variable within the same function
Date: Mon, 15 Sep 2014 22:31:00 -0000	[thread overview]
Message-ID: <bug-63272-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 63272
           Summary: GCC should warn when using pointer to dead scoped
                    variable within the same function
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: jacob.benoit.1 at gmail dot com

Created attachment 33497
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33497&action=edit
testcase

Consider this testcase:

int foo(int i)
{
  int *p = 0;

  if (i)
  {
    int k = i;
    p = &k;
  } /* end of nested scope, k dies, p becomes a dangling pointer */

  return p ? *p : 0; /* the compiler should warn that p points to dead k */
}

Neither Clang 3.4 nor GCC 4.8 currently generate a warning. Yet, since all is
local to this function, it seems like something that a compiler could easily
warn against, and that would have saved me some time today!

Also see LLVM bug: http://llvm.org/bugs/show_bug.cgi?id=20952


             reply	other threads:[~2014-09-15 22:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-15 22:31 jacob.benoit.1 at gmail dot com [this message]
2014-09-16  6:14 ` [Bug c/63272] " manu at gcc dot gnu.org
2020-10-30 10:06 ` dcb314 at hotmail dot com
2021-11-01 22:21 ` msebor at gcc dot gnu.org
2021-12-16 23:31 ` msebor at gcc dot gnu.org
2021-12-17  9:06 ` [Bug middle-end/63272] " dcb314 at hotmail dot com
2022-01-15 23:46 ` cvs-commit at gcc dot gnu.org
2022-01-16  0:04 ` msebor at gcc dot gnu.org
2024-04-09  7:32 ` pinskia at gcc dot gnu.org
2024-04-09  7:33 ` pinskia 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-63272-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).