#49968 [Fbk->Opn]: php 5.2.11 with suhosin and mhash.so enabled causes canary mismatch

ID: 49968 User updated by: ciny at synapsia dot sk Reported By: ciny at synapsia dot sk -Status: Feedback +Status: Open Bug Type: mhash related Operating System: FreeBSD 7.2 amd64 PHP Version: 5.2.11 New Comment: 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. Previous Comments: ------------------------------------------------------------------------ [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> ------------------------------------------------------------------------ [2009-10-23 10:15:52] jani@php.net Thank you for this bug report. To properly diagnose the problem, we need a backtrace to see what is happening behind the scenes. To find out how to generate a backtrace, please read http://bugs.php.net/bugs-generating-backtrace.php for *NIX and http://bugs.php.net/bugs-generating-backtrace-win32.php for Win32 Once you have generated a backtrace, please submit it to this bug report and change the status back to "Open". Thank you for helping us make PHP better. ------------------------------------------------------------------------ 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