public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "b.stanimirov at abv dot bg" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/108118] New: std::weak_ptr lacks a self-usurp check on move Date: Thu, 15 Dec 2022 08:02:45 +0000 [thread overview] Message-ID: <bug-108118-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108118 Bug ID: 108118 Summary: std::weak_ptr lacks a self-usurp check on move Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: b.stanimirov at abv dot bg Target Milestone: --- If one somehow move-assigns a weak pointer to itself, it gets destroyed. Demo: https://godbolt.org/z/eWdhYMhYe
next reply other threads:[~2022-12-15 8:02 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-15 8:02 b.stanimirov at abv dot bg [this message] 2022-12-15 8:41 ` [Bug libstdc++/108118] " pinskia at gcc dot gnu.org 2022-12-15 8:51 ` pinskia at gcc dot gnu.org 2022-12-15 8:53 ` pinskia at gcc dot gnu.org 2022-12-15 9:33 ` redi at gcc dot gnu.org 2022-12-15 9:36 ` redi at gcc dot gnu.org 2022-12-16 14:30 ` cvs-commit at gcc dot gnu.org 2023-01-06 12:07 ` redi at gcc dot gnu.org 2023-03-28 23:35 ` cvs-commit at gcc dot gnu.org 2023-05-16 12:50 ` cvs-commit at gcc dot gnu.org 2023-05-16 15:03 ` redi at gcc dot gnu.org 2023-06-23 16:13 ` cvs-commit at gcc dot gnu.org 2023-06-23 16:19 ` 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-108118-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).