public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/109889] [13/14 Regression] Segfault in __run_exit_handlers since r13-5309-gc3c6c307792026 Date: Wed, 17 May 2023 15:50:33 +0000 [thread overview] Message-ID: <bug-109889-4-8bTmQVda2Y@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109889-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109889 --- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> --- When the function returns the iterator's destructor should detach itself from the sequence's list of iterators, so that it doesn't outlive the stack frame containing the iterator. The commit that caused the regression included this change: _GLIBCXX_DEBUG_VERIFY(this->_M_incrementable(), _M_message(__msg_bad_inc) ._M_iterator(*this, "this")); - _Safe_iterator __ret = *this; + _Safe_iterator __ret(*this, _Unchecked()); ++*this; return __ret; } Maybe this affects how/when the __ret object gets destroyed, so it fails to detach itself.
next prev parent reply other threads:[~2023-05-17 15:50 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-17 11:10 [Bug libstdc++/109889] New: " redi at gcc dot gnu.org 2023-05-17 11:17 ` [Bug libstdc++/109889] " redi at gcc dot gnu.org 2023-05-17 11:25 ` jakub at gcc dot gnu.org 2023-05-17 11:26 ` redi at gcc dot gnu.org 2023-05-17 11:30 ` redi at gcc dot gnu.org 2023-05-17 15:04 ` tuliom at ascii dot art.br 2023-05-17 15:10 ` tuliom at ascii dot art.br 2023-05-17 15:50 ` redi at gcc dot gnu.org [this message] 2023-05-17 15:57 ` redi at gcc dot gnu.org 2023-05-17 15:58 ` redi at gcc dot gnu.org 2023-05-17 15:59 ` redi at gcc dot gnu.org 2023-05-17 19:38 ` rguenth at gcc dot gnu.org 2023-05-19 12:49 ` redi at gcc dot gnu.org 2023-05-24 12:04 ` redi at gcc dot gnu.org 2023-07-27 9:26 ` rguenth at gcc dot gnu.org 2024-05-21 9:15 ` [Bug libstdc++/109889] [13/14/15 " jakub 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-109889-4-8bTmQVda2Y@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).