[Bug c++/91777] No warning for iterator going out of scope

2022-02-24 Thread egallager at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91777 Eric Gallager changed: What|Removed |Added Resolution|--- |WONTFIX Status|WAITING

[Bug c++/91777] No warning for iterator going out of scope

2019-12-22 Thread egallager at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91777 --- Comment #8 from Eric Gallager --- (In reply to Jonathan Wakely from comment #7) > It's also diagnosed by libstdc++ Debug Mode: > > /home/jwakely/gcc/10/include/c++/10.0.0/debug/safe_iterator.h:294: > In function: >

[Bug c++/91777] No warning for iterator going out of scope

2019-09-23 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91777 --- Comment #7 from Jonathan Wakely --- It's also diagnosed by libstdc++ Debug Mode: /home/jwakely/gcc/10/include/c++/10.0.0/debug/safe_iterator.h:294: In function: __gnu_debug::_Safe_iterator<_Iterator, _Sequence, _Category>::reference

[Bug c++/91777] No warning for iterator going out of scope

2019-09-17 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91777 --- Comment #6 from Andrew Pinski --- So here is the thing. Tracking things via memory is hard.

[Bug c++/91777] No warning for iterator going out of scope

2019-09-17 Thread Hi-Angel at yandex dot ru
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91777 --- Comment #5 from Konstantin Kharlamov --- (In reply to Martin Liška from comment #4) > (In reply to Konstantin Kharlamov from comment #3) > > (In reply to Martin Liška from comment #2) > > > I can see a ASAN error: > > > > Correct. You set

[Bug c++/91777] No warning for iterator going out of scope

2019-09-17 Thread marxin at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91777 --- Comment #4 from Martin Liška --- (In reply to Konstantin Kharlamov from comment #3) > (In reply to Martin Liška from comment #2) > > I can see a ASAN error: > > Correct. You set the report status to WAITING: do you expect some answer > from

[Bug c++/91777] No warning for iterator going out of scope

2019-09-17 Thread Hi-Angel at yandex dot ru
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91777 --- Comment #3 from Konstantin Kharlamov --- (In reply to Martin Liška from comment #2) > I can see a ASAN error: Correct. You set the report status to WAITING: do you expect some answer from me, or was it accidental?

[Bug c++/91777] No warning for iterator going out of scope

2019-09-16 Thread marxin at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91777 Martin Liška changed: What|Removed |Added Status|UNCONFIRMED |WAITING Last reconfirmed|

[Bug c++/91777] No warning for iterator going out of scope

2019-09-16 Thread Hi-Angel at yandex dot ru
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91777 --- Comment #1 from Konstantin Kharlamov --- FTR, on IRC was referenced the following paper that may be interesting for implementors https://github.com/isocpp/CppCoreGuidelines/blob/master/docs/Lifetime.pdf