public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "charlie at charliedyson dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/64429] New: Double free when returning std::string from trivial lambda Date: Sun, 28 Dec 2014 18:17:00 -0000 [thread overview] Message-ID: <bug-64429-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64429 Bug ID: 64429 Summary: Double free when returning std::string from trivial lambda Product: gcc Version: 4.8.3 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: charlie at charliedyson dot net The following causes a double free on gcc 4.8.2 as shipped with Ubuntu, and various other versions I tested on Wandbox. Interestingly enough, explicitly copying the string inside the lambda seems to fix it. Code: #include <string> using F = std::string(*)(std::string); std::string call_fn_pointer(F f, std::string s) { return f(s); } std::string f(std::string s) { return s; } int main() { // fine call_fn_pointer(f, "foo"); // fine call_fn_pointer([] (std::string s) { return std::string(s); }, "foo"); // double free call_fn_pointer([] (std::string s) { return s; }, "foo"); } Invocation: $ g++ -std=c++1y foo.cpp -o foo -Wall $ ./foo *** Error in `./foo': double free or corruption (fasttop): 0x08372008 *** Aborted Apologies in advance if I've found another duplicate! Could this relate to 64329?
next reply other threads:[~2014-12-28 18:17 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-12-28 18:17 charlie at charliedyson dot net [this message] 2014-12-29 0:02 ` [Bug c++/64429] " 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-64429-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: 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).