Re: Memory Leak
From: Matthew D. Fuller (fullermd_at_over-yonder.net)
Date: 05/22/04
- Previous message: Simon Barner: "Looking for a ports committer for valgrind (Re: Memory Leak)"
- In reply to: Tim Kientzle: "Re: Memory Leak"
- Next in thread: M. Warner Losh: "Re: Memory Leak"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sat, 22 May 2004 15:13:30 -0500 To: Tim Kientzle <kientzle@freebsd.org>
On Sat, May 22, 2004 at 11:52:19AM -0700 I heard the voice of
Tim Kientzle, and lo! it spake thus:
>
> The one problem I've had is that dmalloc.h redefines some standard
> functions, which can cause gcc to complain.
I usually just have a flag in my Makefile to enable dmalloc (adding a
-D to the cc line to enable including the header file which is inside
#ifdef's, adding the linking of the library, etc), which turns off all
-W flags. gcc's quiet about it then.
Personally, I find its insistence that free(NULL); is an error to be
far more irritating. There's a config flag for it somewhere in the
compile process, though.
-- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ "The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet" _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"
- Previous message: Simon Barner: "Looking for a ports committer for valgrind (Re: Memory Leak)"
- In reply to: Tim Kientzle: "Re: Memory Leak"
- Next in thread: M. Warner Losh: "Re: Memory Leak"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|