Re: Re: Push Request #21
| From: | Yasuo Ohgaki | Date: | Thu, 12 Apr 2012 02:39:20 +0000 |
| Subject: | Re: Re: Push Request #21 | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-59777@lists.php.net to get a copy of this message | ||
Hi
2012/4/12 Stas Malyshev <smalyshev@sugarcrm.com>:
> 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.
You might want to do something like
USE_ZEND_ALLOC=0 ZEND_DONT_UNLOAD_MODULES=1
TEST_PHP_EXECUTABLE=./sapi/cli/php php ./run-tests.php -m ext/openssl/
It seems your API is good.
Isn't it just there aren't people who would like to
responsible?
Regards,
--
Yasuo Ohgaki
yohgaki@ohgaki.net