This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: libstdc++/6246: gcc generates code that memleaks
- From: Carlo Wood <carlo at alinoe dot com>
- To: Clemens Kirchgatterer <clemens at thf dot ath dot cx>
- Cc: rodrigc at gcc dot gnu dot org, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, gcc-gnats at gcc dot gnu dot org
- Date: Mon, 15 Apr 2002 03:51:05 +0200
- Subject: Re: libstdc++/6246: gcc generates code that memleaks
- References: <20020413020226.31948.qmail@sources.redhat.com> <20020413082934.183ee4d6.clemens@thf.ath.cx>
On Sat, Apr 13, 2002 at 08:29:34AM +0200, Clemens Kirchgatterer wrote:
> hmm, this is very strange, as it is NOT gcc's fault, but mine.
>
> *buf += str.str(); <-- this freazes the buffer and returns a
> pointer to it. the caller is now
> responsible for freeing it with delete().
No it doesn't, not since 3.0 which is conforming to the standard
and where str() returns a std::string. Use std::stringstream,
not std::strstream.
--
Carlo Wood <carlo@alinoe.com>