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
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. ;-
Stanislav Malyshev wrote:
Hi!
I'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
i
John Carter -X (johncart - PolicyApp Ltd at Cisco) wrote:
Shire,
Xlog looks really useful. Does it also help with "exception thrown
without a stack trace"?
Thanks John,
I was just made aware that xdebug has similar functionality with a little bit
different approach, config, etc so do check
Hi!
I'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
proj
Shire,
Xlog looks really useful. Does it also help with "exception thrown
without a stack trace"?
Thanks,
John.
-Original Message-
From: shire [mailto:sh...@tekrat.com]
Sent: 19 January 2009 01:45
To: PHP Internals List
Subject: [PHP-DEV] PATCH: zend_mm_heap_overfl
I'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 a
