Edit report at https://bugs.php.net/bug.php?id=60038&edit=1
ID: 60038 Updated by: larue...@php.net Reported by: larue...@php.net Summary: SIGALRM cause segfault in php_error_cb -Status: Assigned +Status: Closed Type: Bug Package: Scripting Engine problem -PHP Version: 5.3.8 +PHP Version: 5.4.0beta1 Assigned To: laruence Block user comment: N Private report: N New Comment: This bug has been fixed in SVN. Snapshots of the sources are packaged every three hours; this change will be in the next snapshot. You can grab the snapshot at http://snaps.php.net/. For Windows: http://windows.php.net/snapshots/ Thank you for the report, and for helping us make PHP better. Previous Comments: ------------------------------------------------------------------------ [2011-10-16 03:00:51] larue...@php.net Automatic comment from SVN on behalf of laruence Revision: http://svn.php.net/viewvc/?view=revision&revision=318145 Log: Fixed bug #60038 (SIGALRM cause segfault in php_error_cb) ------------------------------------------------------------------------ [2011-10-13 00:44:06] larue...@php.net updated patch, signal block mechanism only take effect when zend signal enabled. ------------------------------------------------------------------------ [2011-10-13 00:42:48] larue...@php.net The following patch has been added/updated: Patch Name: bug60038.patch Revision: 1318466568 URL: https://bugs.php.net/patch-display.php?bug=60038&patch=bug60038.patch&revision=1318466568 ------------------------------------------------------------------------ [2011-10-11 09:31:54] larue...@php.net Assign to myself, if there is no objections in ML, I will apply the patch. ------------------------------------------------------------------------ [2011-10-11 09:27:18] larue...@php.net actully, there are two issue about this segfault I have explained before in my blog: http://www.laruence.com/2011/01/27/1854.html and http://www.laruence.com/2008/12/31/647.html so the point is do you think this is worth fixing? ------------------------------------------------------------------------ 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 https://bugs.php.net/bug.php?id=60038 -- Edit this bug report at https://bugs.php.net/bug.php?id=60038&edit=1
