[Bug c++/83414] Successive calls to "new" return the same pointer

2017-12-14 Thread pmsf at ufc dot br
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83414 --- Comment #4 from Pablo M. S. Farias --- Thank you for the instructions; I'll follow them from now on. Sorry for the inconveniences.

[Bug c++/83414] Successive calls to "new" return the same pointer

2017-12-14 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83414 --- Comment #3 from Jonathan Wakely --- A class that uses new/delete but doesn't have a proper copy constructor defined is a massive red flag, and that should have been obvious. Instead of blaming GCC you could have found this using valgrind:

[Bug c++/83414] Successive calls to "new" return the same pointer

2017-12-14 Thread pmsf at ufc dot br
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83414 Pablo M. S. Farias changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug c++/83414] Successive calls to "new" return the same pointer

2017-12-14 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83414 Richard Biener changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|