Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: leonleon77 at gmail dot com
Target Milestone: ---
From a small thread on the gcc-help mailing list
https://gcc.gnu.org/ml/gcc-help/2020-03/msg3.html
( btw
: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: leonleon77 at gmail dot com
Target Milestone: ---
When in Debug Mode (-D_GLIBCXX_DEBUG) there is a racing condition between
destructor of a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91910
--- Comment #2 from leon ---
(In reply to Andrew Pinski from comment #1)
> Seems like this is a bug in the testcase rather than libstdc++.
>
> >exemplifying concurrent destruction of iterator and container
> That seems like a disaster waiting to
dot org
ReportedBy: leonleon77 at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42446