public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "noah at vectorized dot io" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/101367] [coroutines] destructor for capture in lambda temporary operand to co_yield expression called twice Date: Wed, 07 Jul 2021 16:18:08 +0000 [thread overview] Message-ID: <bug-101367-4-MNpIWNzI8V@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101367-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101367 --- Comment #1 from Noah Watkins <noah at vectorized dot io> --- In the reproducer there are no errors for: generator<int> f() { co_yield resource{[]{}}; } but `free(): invalid pointer` occurs for: generator<int> f() { std::string s; co_yield resource{[s]{}}; }
next prev parent reply other threads:[~2021-07-07 16:18 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-07 16:16 [Bug c++/101367] New: " noah at vectorized dot io 2021-07-07 16:18 ` noah at vectorized dot io [this message] 2021-08-09 0:40 ` [Bug c++/101367] " davidledger at live dot com.au 2021-08-09 1:09 ` noah at vectorized dot io 2021-08-10 3:06 ` davidledger at live dot com.au 2021-08-10 3:59 ` noah at vectorized dot io 2021-10-01 19:18 ` iains at gcc dot gnu.org 2022-12-04 10:41 ` cvs-commit 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-101367-4-MNpIWNzI8V@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).