Date: Mon, 29 Apr 2002 02:50:41 -0700 (PDT) From: Brad Knotwell <knotwell@ix.netcom.com> To: freebsd-bugs@FreeBSD.org Subject: bin/37461: memory leak in snprintf and vsnprintf Message-ID: <200204290950.g3T9ofr16633@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/37461; it has been noted by GNATS. From: Brad Knotwell <knotwell@ix.netcom.com> To: freebsd-gnats-submit@FreeBSD.org Cc: Subject: bin/37461: memory leak in snprintf and vsnprintf Date: Thu, 25 Apr 2002 10:42:07 -0700 (PDT) >Number: 37461 >Category: bin >Synopsis: memory leak in snprintf and vsnprintf >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Apr 25 10:50:02 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Brad Knotwell >Release: 4.5 >Organization: home >Environment: FreeBSD fiordland.brad.net 4.5-STABLE FreeBSD 4.5-STABLE #0: Mon Jan 28 14:51:47 PST 2002 root@magellan.brad.net:/usr/obj/usr/src/sys/BRAD i386 >Description: Since I've already done a send-pr for NetBSD that explains the problem, I'll just post a link: http://www.NetBSD.org/cgi-bin/query-pr-single.pl?number=16483 Remarkably, the commit log for snprintf.c indicates this problem (or an extremely close approximation; I was leaking in __smakebuf as well) was reported against 4.2, fixed, the PR (#26044) closed, and then unfixed. >How-To-Repeat: >Fix: I worked around the problem using a 1-character buffer. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200204290950.g3T9ofr16633>