#49968 [Opn->Fbk]: php 5.2.11 with suhosin and mhash.so enabled causes canary mismatch
| From: | jani@php.net | Date: | Fri, 23 Oct 2009 12:36:21 +0000 |
| Subject: | #49968 [Opn->Fbk]: php 5.2.11 with suhosin and mhash.so enabled causes canary mismatch | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-143844@lists.php.net to get a copy of this message | ||
ID: 49968
Updated by: jani@php.net
Reported By: ciny at synapsia dot sk
-Status: Open
+Status: Feedback
Bug Type: mhash related
Operating System: FreeBSD 7.2 amd64
PHP Version: 5.2.11
New Comment:
You can't run the thing on command line..? I thought that's how you
really meant it to be reproduced: # php -v ? (please don't reply before
you have real feedback)
Previous Comments:
------------------------------------------------------------------------
[2009-10-23 12:33:52] ciny at synapsia dot sk
it was with suhosin patch compiled in but with USE_ZEND_ALLOC set to 0.
I can post a test without suhosin but that will have to wait until
night - I see this behaviour on a production machine so I can not allow
php to segfault during work hours and I don't have a spare one to
reproduce the problem.
------------------------------------------------------------------------
[2009-10-23 12:08:43] jani@php.net
Was the backtrace with or without the suhosin patch? (I'm guessing
without?)
------------------------------------------------------------------------
[2009-10-23 11:38:46] ciny at synapsia dot sk
if by 3rd party patch you mean suhosin then yes, bud instead of the
error message it segfaults.
------------------------------------------------------------------------
[2009-10-23 11:00:07] jani@php.net
Proper link: http://www.pastebin.cz/43ef1b43ee1dbd
And obvious question: Does it crash without that 3rd party patch?
------------------------------------------------------------------------
[2009-10-23 10:24:08] ciny at synapsia dot sk
<a href="http://www.pastebin.cz/43ef1b43ee1dbd">
here is the gdb output
</a>
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/49968
--
Edit this bug report at http://bugs.php.net/?id=49968&edit=1