Den 2018-10-11 kl. 23:25, skrev Julien Pauli:
On Tue, Oct 9, 2018 at 10:56 AM Rowan Collins
wrote:
On Tue, 9 Oct 2018 at 07:16, Dmitry Stogov wrote:
Hi Rowan,
This error message is triggered when Zend MM used in improper way, e.g.
invalid pointer free, etc.
MM can't provide useful
On Tue, Oct 9, 2018 at 10:56 AM Rowan Collins
wrote:
> On Tue, 9 Oct 2018 at 07:16, Dmitry Stogov wrote:
>
> > Hi Rowan,
> >
> >
> > This error message is triggered when Zend MM used in improper way, e.g.
> > invalid pointer free, etc.
> >
> > MM can't provide useful information about the
On Tue, 9 Oct 2018 at 07:16, Dmitry Stogov wrote:
> Hi Rowan,
>
>
> This error message is triggered when Zend MM used in improper way, e.g.
> invalid pointer free, etc.
>
> MM can't provide useful information about the context and reason.
>
I get that it can't provide the *reason*, but that
...
In most cases valgrind will show incorrect MM operations and their history.
Thanks. Dmitry.
From: Rowan Collins
Sent: Monday, October 8, 2018 1:17:06 PM
To: PHP internals
Subject: [PHP-DEV] die('zend_mm_heap corrupted'); // TODO: Better error message
Hi all
Hi all,
We recently had an error in production which was hard to reproduce, hard to
debug, and turned out to be a bug in an extension. One of the oddest
symptoms was that the PHP code seemed to run to completion, but the request
was never logged by Apache.
The only thing logged was the words
