public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: richard@ex-parrot.com
To: gcc-gnats@gcc.gnu.org
Subject: optimization/5006: Multiple temporary objects created on stack in the same location.
Date: Tue, 04 Dec 2001 03:26:00 -0000	[thread overview]
Message-ID: <20011204111601.24198.qmail@sources.redhat.com> (raw)


>Number:         5006
>Category:       optimization
>Synopsis:       Multiple temporary objects created on stack in the same location.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          wrong-code
>Submitter-Id:   net
>Arrival-Date:   Tue Dec 04 03:26:01 PST 2001
>Closed-Date:
>Last-Modified:
>Originator:     Richard Smith
>Release:        3.0.2 (and 3.0.1)
>Organization:
>Environment:
i686-pc-linux-gnu
>Description:
When compiling with -O, the compiler creates a temporary object of type auto_ptr<A> on the stack.  It then overwrites this with a temporary of type A before calling the destructor on the original auto_ptr<A>.  This tries to call ::operator delete() on what it thinks is the heap-allocated pointer owned by the auto_ptr but is actually a string literal owned by A.  Depending on the exact memory layout, a segv sometimes results.
>How-To-Repeat:
Build with -O to duplicate the bug.  A run-time segv (usually) results.
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2001-12-04 11:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-04  3:26 richard [this message]
2002-03-19  4:46 Richard Smith
2002-04-03  1:21 rth

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=20011204111601.24198.qmail@sources.redhat.com \
    --to=richard@ex-parrot.com \
    --cc=gcc-gnats@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).