home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.sources.wanted:5076 comp.software-eng:4339 comp.sys.sun.apps:2496
- Path: sparky!uunet!usc!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!usenet.ins.cwru.edu!agate!doc.ic.ac.uk!uknet!mucs!m1!bevan
- From: bevan@cs.man.ac.uk (Stephen J Bevan)
- Newsgroups: comp.sources.wanted,comp.software-eng,comp.sys.sun.apps
- Subject: Re: Purify & Sentinel
- Message-ID: <BEVAN.92Nov17002108@beluga.cs.man.ac.uk>
- Date: 17 Nov 92 00:21:08 GMT
- References: <1992Nov2.212558.28104@pure.com> <1992Nov13.074039@eklektix.com>
- <HAMM.92Nov13113222@toto.austoto.sps.mot.com>
- Sender: news@cs.man.ac.uk
- Followup-To: comp.sources.wanted
- Organization: Department of Computer Science, University of Manchester
- Lines: 14
- In-reply-to: hamm@austoto.sps.mot.com's message of 13 Nov 92 11:32:22 GMT
-
- In article <HAMM.92Nov13113222@toto.austoto.sps.mot.com> hamm@austoto.sps.mot.com (Steve Hamm) writes:
-
- With regard to leak detection, we've reduced our leaks by over 90%
- using Purify, which for us amounted to megabytes, sometimes.
-
- Was any other debuggging system previously in use? If so, what sort
- of leaks did Purify catch that the other system didn't%? If you
- weren't using another debugging package, shame on you :-).
-
- bevan
-
- % Note I'm not interested in errors such as failing to free memory and
- freeing memory multiple times since I can check those with a
- homebrew solution of my own.
-