Re: PATCH: zend_mm_heap_overflow()
| From: | shire | Date: | Mon, 19 Jan 2009 21:07:20 +0000 |
| Subject: | Re: PATCH: zend_mm_heap_overflow() | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-42712@lists.php.net to get a copy of this message | ||
Stanislav Malyshev wrote:
Hi!Yes, I like this idea better as it's more flexible but I wasn't sure if we wanted that much visibility into the global variables of the allocator. I suppose though, as with other things of this nature, if you're mucking with this data then you should be doing so at your own risk etc. ;-) -shireI'm releasing an extended PHP logging extension that we currently use at facebook with much success. I currently use a small patch to determine if a memory overflow has occurred as there's currently no direct access into the allocator structures. You can get more information on the project at http://tekrat.com/php/xlog/.Maybe just make AG() exported?