[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Mem Leak Tracer (monitored malloc)
- To: linux ILUG <linux-il(at-nospam)linux.org.il>
- Subject: Re: Mem Leak Tracer (monitored malloc)
- From: Oleg Goldshmidt <ogoldshmidt(at-nospam)computer.org>
- Date: 22 Nov 2001 23:36:26 -0500
- Delivered-To: linux.org.il-linux-il@linux.org.il
- In-Reply-To: <E166z27-0002y5-00@witch.dyndns.org>
- Organization: Speaking for myself only.
- Original-Sender: ogoldshmidt@computer.org
- References: <E9F3EF9AD316D511A5150002A55110B801425F7E@exchil03.mercury.co.il><E166z27-0002y5-00@witch.dyndns.org>
- Reply-To: linux-il(at-nospam)linux.org.il
- Sender: ogoldshmidt(at-nospam)computer.org
- Sender: linux-il-bounce(at-nospam)cs.huji.ac.il
- User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Cuyahoga Valley)
Hetz Ben Hamo <hetz@kde.org> writes:
> Oh, and insure sucks, specially when it finds tons of other leaks,
> but not in your code, in the other libs code ;)
I didn't see that all that much, and when it happened it was simple
to make it shut up about the particular things.
One thing about Insure - it is only usable as a debugging tool,
not as a real compiler. The way we used to use it was: compile
with a real compiler (gcc) for production, but never let anything
"un-Insured" into production.
--
Oleg Goldshmidt | ogoldshmidt@NOSPAM.computer.org
If it aint't broken it hasn't got enough features yet.
=================================================================
To unsubscribe, send mail to linux-il-request@linux.org.il with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail linux-il-request@linux.org.il