From owner-freebsd-current@FreeBSD.ORG Sat Oct 7 01:13:23 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EEF2E16A5D6 for ; Sat, 7 Oct 2006 01:13:23 +0000 (UTC) (envelope-from sean-freebsd@farley.org) Received: from mail.farley.org (farley.org [67.64.95.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8CF3C43D49 for ; Sat, 7 Oct 2006 01:13:23 +0000 (GMT) (envelope-from sean-freebsd@farley.org) Received: from dhcp1.farley.org (dhcp1.farley.org [192.168.1.101]) by mail.farley.org (8.13.8/8.13.8) with ESMTP id k971EKmZ004390 for ; Fri, 6 Oct 2006 20:14:20 -0500 (CDT) (envelope-from sean-freebsd@farley.org) Date: Fri, 6 Oct 2006 20:13:25 -0500 (CDT) From: "Sean C. Farley" To: freebsd-current@freebsd.org Message-ID: <20061006200320.T1063@baba.farley.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Fix for memory leak in setenv/unsetenv X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Oct 2006 01:13:24 -0000 Many a moon ago[1], I put together a patch to fix the leak in setenv() and unsetenv(). A few months ago, I submitted a PR (kern/99826[2]) for the final fix. I was wondering if anyone would take a look at it to see if any changes are still warranted. The PR contains information about the patch and sample programs to test it out. Thank you. Sean 1. http://lists.freebsd.org/pipermail/freebsd-hackers/2005-February/010463.html 2. http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/99826 -- sean-freebsd@farley.org