This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/52967] Segmentation fault on std::vector destruction
- From: "redi at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 13 Apr 2012 09:52:03 +0000
- Subject: [Bug c++/52967] Segmentation fault on std::vector destruction
- Auto-submitted: auto-generated
- References: <bug-52967-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52967
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |INVALID
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-04-13 09:52:03 UTC ---
Yes, this is invalid. If you want to do this then you need to call reserve on
the vector so that push_back doesn't cause reallocation (or decide if the code
shouldn't just be rewritten differently!)