This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Memory leak in ios.cc:326

From: Benjamin Kosnik <bkoz at redhat dot com>
To: Loren James Rittle <rittle at latour dot rsch dot comm dot mot dot com>
Cc: libstdc++ at gcc dot gnu dot org, weigand at immd1 dot informatik dot uni-erlangen dot de
Date: Fri, 28 Mar 2003 09:29:42 -0600
Subject: Re: Memory leak in ios.cc:326
References: <200303262150.WAA23290@faui11.informatik.uni-erlangen.de><200303272114.h2RLEMeb049465@latour.rsch.comm.mot.com>

>I have my hands full at the moment, but I wanted to ACK this message.

Me too. I'm going to take a break from the 27_io testsuite and scope
this a bit today.

There's one test case for callbacks, I'm using that. Looking at this on
3.2, with GLIBCPP_FORCE_NEW, everything looks ok. But on 3.4, I'm seeing
some issues with constructing the locale cache for the standard streams.
I suspect this is also the issue for 3.3.

Anyway. 

Carlo is right, debugging is a mess right now for mainline. I can core
gdb very quickly on a variety of hardware and linux distros (stepping
into std::ios construction, for one).  It looks like gdb-5.2 works much
better than either mainline gdb, other gdb branches, or the last gdb
release.

best,
benjamin

Follow-Ups:
- Re: Memory leak in ios.cc:326
  - From: Carlo Wood
- Re: Memory leak in ios.cc:326
  - From: Ulrich Weigand

References:
- Re: Memory leak in ios.cc:326
  - From: Ulrich Weigand
- Re: Memory leak in ios.cc:326
  - From: Loren James Rittle

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]