From owner-freebsd-bugs Tue Jan 28 12:30: 6 2003 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 31D4337B405 for ; Tue, 28 Jan 2003 12:30:05 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id D312943F75 for ; Tue, 28 Jan 2003 12:30:04 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.6/8.12.6) with ESMTP id h0SKU4NS075442 for ; Tue, 28 Jan 2003 12:30:04 -0800 (PST) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.6/8.12.6/Submit) id h0SKU4WE075441; Tue, 28 Jan 2003 12:30:04 -0800 (PST) Date: Tue, 28 Jan 2003 12:30:04 -0800 (PST) Message-Id: <200301282030.h0SKU4WE075441@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Sean Farley Subject: Re: bin/47599: Memory leak on stdout Reply-To: Sean Farley Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR bin/47599; it has been noted by GNATS. From: Sean Farley To: David Schultz Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: bin/47599: Memory leak on stdout Date: Tue, 28 Jan 2003 14:28:42 -0600 (CST) On Tue, 28 Jan 2003, David Schultz wrote: > Thus spake Sean C. Farley : > > When testing an application for memory leaks, I noticed one that > > I could not get rid of. I happened to be allocated from > > /usr/src/lib/libc/stdio/makebuf.c on line 72, but only when > > printf() (or really any function) used stdout. Adding an > > fclose(stdout) to the end of my application fixed the memory > > leak. > > > > I realize this is not much of a leak, but I thought it would be > > nice to have it either documented or fixed before others run > > into this confusing leak. > > I don't think it's a bug that libc lazily allocates memory for the > three standard file descriptors. I think you should consider this a > false positive from dmalloc. Do you mean lazily deallocates memory? I think the allocation is perfectly fine. I was just wondering if there is a point at which libc was supposed to free the memory before exit. A hook similar to atexit()? Sean ----------------------- sean-freebsd@farley.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message