This is the mail archive of the
gcc-prs@gcc.gnu.org
mailing list for the GCC project.
Re: libstdc++/1853: <deque> deallocates unowned memory within .pop_back()
- From: pme at gcc dot gnu dot org
- To: gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org, pme at gcc dot gnu dot org, stevemw at place dot org
- Date: 28 Dec 2001 23:51:11 -0000
- Subject: Re: libstdc++/1853: <deque> deallocates unowned memory within .pop_back()
- Reply-to: pme at gcc dot gnu dot org, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org, pme at gcc dot gnu dot org, stevemw at place dot org, gcc-gnats at gcc dot gnu dot org
Synopsis: <deque> deallocates unowned memory within .pop_back()
Responsible-Changed-From-To: unassigned->pme
Responsible-Changed-By: pme
Responsible-Changed-When: Fri Dec 28 15:51:10 2001
Responsible-Changed-Why:
I changed it. Still an issue as of today. The internals of
deque aren't documented very well at all. I want to figure
out what memory games are being played before changing the
code; the obvious solution may be too slow.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=1853