public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "benjamin.kircher at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/55320] New: Invalid delete with throwing copy-c'tor passed to std::function
Date: Wed, 14 Nov 2012 07:58:00 -0000	[thread overview]
Message-ID: <bug-55320-4@http.gcc.gnu.org/bugzilla/> (raw)


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55320

             Bug #: 55320
           Summary: Invalid delete with throwing copy-c'tor passed to
                    std::function
    Classification: Unclassified
           Product: gcc
           Version: 4.7.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: benjamin.kircher@gmail.com


Created attachment 28682
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=28682
Example program

The example program attached compiles w/o warnings and crashes with an invalid
delete when executed.


$ gcc --version
gcc (Debian 4.7.2-4) 4.7.2


$ cat main.cpp
#include <functional>
#include <stdexcept>
#include <iostream>
#include <ostream>

struct functor
{
    functor() = default;
    functor(const functor&) { throw std::exception(); }
    void operator()() {}
};

int main()
try
{
    std::function<void()> func = functor();
    return 0;
}
catch (std::exception&)
{
    std::cout << "catched" << std::endl;
}


Valgrind gives me
$ valgrind --tool=memcheck ./a.out
<snip>
==...== Invalid free() / delete / delete[] / realloc()
==...==    at 0x...: operator delete(void*) (in
/usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
==...==    by 0x...:
std::_Function_base::_Base_manager<functor>::_M_destroy(std::_Any_data&,
std::integral_constant<bool, false>) (functional:1780)
==...==    by 0x...:
std::_Function_base::_Base_manager<functor>::_M_manager(std::_Any_data&,
std::_Any_data const&, std::_Manager_operation) (functional:1804)
==...==    by 0x...: std::_Function_base::~_Function_base() (functional:1885)
==...==    by 0x...: std::function<void ()>::function<functor>(functor,
std::enable_if<!(std::is_integral<functor>::value), std::function<void
()>::_Useless>::type) (functional:2292)
<snip>

On clang/libc++ this behaves as expected.


             reply	other threads:[~2012-11-14  7:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-14  7:58 benjamin.kircher at gmail dot com [this message]
2012-11-14  8:10 ` [Bug libstdc++/55320] " benjamin.kircher at gmail dot com
2012-11-14  9:46 ` daniel.kruegler at googlemail dot com
2012-11-14 10:43 ` paolo.carlini at oracle dot com
2012-11-14 11:43 ` redi at gcc dot gnu.org
2012-11-14 12:12 ` redi at gcc dot gnu.org
2012-11-14 23:33 ` redi at gcc dot gnu.org
2012-11-15  0:21 ` redi at gcc dot gnu.org
2012-11-15  0:23 ` 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-55320-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).