public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "blubban at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/105804] New: List-initialized argument in await expression is doubly freed
Date: Wed, 01 Jun 2022 15:14:48 +0000	[thread overview]
Message-ID: <bug-105804-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105804

            Bug ID: 105804
           Summary: List-initialized argument in await expression is
                    doubly freed
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: blubban at gmail dot com
  Target Milestone: ---

#include <coroutine>
#include <memory>

struct my_params {
        std::unique_ptr<int> ptr; // or any other object with nontrivial dtor
};

static std::suspend_never take_params(my_params params)
{
        return {};
}

struct coro_t {
        struct promise_type {
                coro_t get_return_object() { return {}; }
                std::suspend_never initial_suspend() { return {}; }
                std::suspend_never final_suspend() noexcept { return {}; }
                void unhandled_exception() noexcept {}
        };
};

static coro_t my_coro()
{
        co_await take_params({ std::make_unique<int>(5) });
}

int main()
{
        my_coro();
}


Expected output: Same as /bin/true
Actual: free(): double free detected in tcache 2

https://godbolt.org/z/8f9d3TzYo

Probably same root cause as bug 98056 and/or bug 103871, but since the symptoms
are way different (it's a wrong-code, not just rejects-valid), I think it
warrants a separate report.

             reply	other threads:[~2022-06-01 15:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-01 15:14 blubban at gmail dot com [this message]
2023-04-16 18:10 ` [Bug c++/105804] coroutines: " blubban at gmail dot com

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-105804-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).