Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:59775 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 65863 invoked from network); 12 Apr 2012 02:01:46 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 12 Apr 2012 02:01:46 -0000 Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 67.192.241.193 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 67.192.241.193 smtp193.dfw.emailsrvr.com Linux 2.6 Received: from [67.192.241.193] ([67.192.241.193:57667] helo=smtp193.dfw.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 6B/BD-23245-887368F4 for ; Wed, 11 Apr 2012 22:01:46 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp9.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id 5C1553C056E; Wed, 11 Apr 2012 22:01:42 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp9.relay.dfw1a.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 167783C0302; Wed, 11 Apr 2012 22:01:42 -0400 (EDT) Message-ID: <4F863785.7000709@sugarcrm.com> Date: Wed, 11 Apr 2012 19:01:41 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:11.0) Gecko/20120313 Thunderbird/11.0 MIME-Version: 1.0 To: "jason.gerfen@gmail.com" CC: "internals@lists.php.net" References: <0BAF545D-95F6-4C4B-8E03-025E8604B1ED@gmail.com> In-Reply-To: <0BAF545D-95F6-4C4B-8E03-025E8604B1ED@gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Re: Push Request #21 From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > There really doesn't seem to be much interest in this proposed patch. Should I continue development efforts on closing this feature request? Can't say anything here - I don't use these APIs personally, but maybe other people need them. No idea :) > I do also have a few questions regarding standards adherence, and memory leak methods of detection. > > I ask about the memory leak detection as passing test scripts through valgrind only led me to find leaks in the openssl_pkey_new() function. There's two levels of leak detection - internal memory management & valgrind. How to work with them: 1. Internal. Compile php with --enable-debug and run your tests. Leaks will be reported by php. 2. External. Set USE_ZEND_ALLOC environment variable to 0. Set ZEND_DONT_UNLOAD_MODULES to 1. Run it under valgrind, see what it reports. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227