public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "chgros at coverity dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/106812] Throwing a non-copyable exception Date: Fri, 14 Oct 2022 18:18:35 +0000 [thread overview] Message-ID: <bug-106812-4-rN1xmHADbo@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106812-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106812 Charles-Henri Gros <chgros at coverity dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |chgros at coverity dot com --- Comment #4 from Charles-Henri Gros <chgros at coverity dot com> --- It's worse than this, "throw" will even move a non-movable value in the absence of a copy constructor: #include <iostream> #include <memory> using namespace std; int main(int argc, char const * const *argv) { unique_ptr<int> u(new int); cout << "u.get() first: " << (void*)u.get() << endl; try { throw u; } catch(...) { } cout << "u.get() after throw: " << (void*)u.get() << endl; }
prev parent reply other threads:[~2022-10-14 18:18 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-02 7:14 [Bug c++/106812] New: " jens.maurer at gmx dot net 2022-09-02 7:21 ` [Bug c++/106812] " jens.maurer at gmx dot net 2022-09-19 18:53 ` mpolacek at gcc dot gnu.org 2022-09-19 19:01 ` mpolacek at gcc dot gnu.org 2022-10-14 18:18 ` chgros at coverity dot com [this message]
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-106812-4-rN1xmHADbo@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).