public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "potswa at mac dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/56568] New: std::initializer_list return value contents lost prematurely Date: Fri, 08 Mar 2013 08:40:00 -0000 [thread overview] Message-ID: <bug-56568-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56568 Bug #: 56568 Summary: std::initializer_list return value contents lost prematurely Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: potswa@mac.com See http://stackoverflow.com/q/15286450/153285 This program segfaults: #include <string> #include <iostream> #include <initializer_list> int main() { for ( auto && s : []() -> std::initializer_list< std::string > { return { std::string( "first" ), std::string( "second" ) }; }() ) std::cout << s << '\n'; } The return value object should be initialized from the braced-init-list, and bound directly to the implicit "auto && __range" object of the range-based for statement. The array backing that object should have the same lifetime as it, namely the duration of the loop. Instead, the array is destroyed when the lambda exits. This is not easy to fix, but I'll just file this.
next reply other threads:[~2013-03-08 8:40 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-03-08 8:40 potswa at mac dot com [this message] 2015-09-03 21:41 ` [Bug c++/56568] " fuzzyTew at gmail dot com 2015-09-03 21:49 ` redi at gcc dot gnu.org 2015-09-03 23:51 ` fuzzyTew at gmail dot com 2015-09-03 23:53 ` fuzzyTew at gmail dot com 2015-09-04 0:25 ` potswa at mac dot com 2015-09-04 9:02 ` 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-56568-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).