home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.programming
- Path: sparky!uunet!munnari.oz.au!cs.mu.OZ.AU!munta.cs.mu.OZ.AU!fjh
- From: fjh@munta.cs.mu.OZ.AU (Fergus James HENDERSON)
- Subject: Re: Chasing memory leaks: tools, procedures?
- Message-ID: <9220400.530@mulga.cs.mu.OZ.AU>
- Sender: news@cs.mu.OZ.AU
- Organization: Computer Science, University of Melbourne, Australia
- References: <1992Jul6.093355.20442@lth.se> <1992Jul18.203518.14496@murdoch.acc.Virginia.EDU> <1992Jul19.160323.8820@organpipe.uug.arizona.edu> <NICKEL.92Jul19184631@desaster.cs.tu-berlin.de>
- Date: Tue, 21 Jul 1992 14:27:02 GMT
- Lines: 18
-
- nickel@cs.tu-berlin.de (Juergen Nickelsen) writes:
-
- >dave@cs.arizona.edu (Dave Schaumann) writes:
- >> must_alloc() is just a function that calls malloc and aborts if malloc
- >> returns NULL.
- >
- >To make this more useful, must_alloc() should also call some
- >cleanup-function. For some application it is a must to have control of
- >their termination, e.g. to remove temporary files, re-rename
- >temporarily renamed files etc.
-
- Why not just use at_exit() to install an error handler if necessary?
-
- --
- Fergus Henderson fjh@munta.cs.mu.OZ.AU
- This .signature VIRUS is a self-referential statement that is true - but
- you will only be able to consistently believe it if you copy it to your own
- .signature file!
-