On Wed, 10 Jan 2024 at 18:28, François Dumont <frs.dum...@gmail.com> wrote: > > libstdc++: [_GLIBCXX_DEBUG] Fix assignment of value-initialized iterator > [PR112477] > > Now that _M_Detach do not reset iterator _M_version value we need to > reset it when > the iterator is attached to a new sequence. Even if this sequencer is > null like when > assigning a value-initialized iterator. In this case _M_version shall be > reset to 0. > > libstdc++-v3/ChangeLog: > > PR libstdc++/112477 > * src/c++11/debug.cc > (_Safe_iterator_base::_M_attach): Reset _M_version to 0 if > attaching to null > sequence. > (_Safe_iterator_base::_M_attach_single): Likewise. > (_Safe_local_iterator_base::_M_attach): Likewise. > (_Safe_local_iterator_base::_M_attach_single): Likewise. > * testsuite/23_containers/map/debug/112477.cc: New test case. > > Tested under Linux x64 _GLIBCXX_DEBUG mode. > > Ok to commit and backport to gcc 13 ?
Yes please - thanks for the quick fix. > > François > > On 09/01/2024 22:47, fdumont at gcc dot gnu.org wrote: > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112477 > > > > François Dumont <fdumont at gcc dot gnu.org> changed: > > > > What |Removed |Added > > ---------------------------------------------------------------------------- > > Assignee|unassigned at gcc dot gnu.org |fdumont at gcc dot > > gnu.org > > > > --- Comment #8 from François Dumont <fdumont at gcc dot gnu.org> --- > > Hi > > I'm going to have a look but if you wish to contribute do not hesitate. > > Thanks for the report. > >
