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: Freeing xalloc'ed array

From: Phil Edwards <phil at codesourcery dot com>
To: Jonathan Wakely <cow at compsoc dot man dot ac dot uk>
Cc: Paolo Carlini <pcarlini at suse dot de>, Akim Demaille <akim at epita dot fr>, libstdc++ at gcc dot gnu dot org
Date: Wed, 13 Oct 2004 16:40:10 -0400
Subject: Re: Freeing xalloc'ed array
References: <mv4mzyrqamw.fsf@nostromo.lrde.epita.fr> <416CF4BC.6030204@suse.de> <20041013114042.GA5591@compsoc.man.ac.uk>

On Wed, Oct 13, 2004 at 12:40:42PM +0100, Jonathan Wakely wrote:
> On Wed, Oct 13, 2004 at 11:26:20AM +0200, Paolo Carlini wrote:
> 
> > Forgot to add: professional programmer arounds, using  gcc + valgrind often
> > prepare custom suppression files, in order to avoid spurious entries in the
> > valgrind reports (I'm sure they do that at CERN, f.i.)
> 
> I'll mention that too.

Possibly we should ship such a file, at least as a starting point?


-- 
Behind everything some further thing is found, forever; thus the tree behind
the bird, stone beneath soil, the sun behind Urth.  Behind our efforts, let
there be found our efforts.
              - Ascian saying, as related by Loyal to the Group of Seventeen

Follow-Ups:
- Re: Freeing xalloc'ed array
  - From: Benjamin Kosnik

References:
- Freeing xalloc'ed array
  - From: Akim Demaille
- Re: Freeing xalloc'ed array
  - From: Paolo Carlini
- Re: Freeing xalloc'ed array
  - From: Jonathan Wakely

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