ID: 27735 Comment by: josestefan at hotmail dot com Reported By: as at netoholic dot de Status: Bogus Bug Type: Reproducible crash Operating System: Linux PHP Version: 4.3.5 New Comment:
I've noticed that disabling all CustomLog in apache's httpd conf file avoids the crash. So maybe that's a good place for the developers to start looking. I have log_errors = Off on my php.ini file, so it really doesn't make sense to me. But I have confirmed that with the CustomLogs disabled, I get no crashes. running Windows XP, Apache: 2.0.49, PHP: 4.3.5 Previous Comments: ------------------------------------------------------------------------ [2004-03-30 08:50:43] noackjr at alumni dot rice dot edu I have this exact same problem (identical backtrace, etc.) with FreeBSD 5.2.1, Apache 2.0.49, and PHP 4.3.5. Reverting to the PCRE from 4.3.4 (replacing ext/pcre) also resolved the problem for me. Does PCRE 4.5 expose an Apache bug, or is this a problem with PCRE 4.5? If it's the former, leave it as Bogus. Otherwise, this is a PHP bug because it's bundled code. ------------------------------------------------------------------------ [2004-03-30 06:57:35] chb at muc dot de I don't think this bug is "Bogus". I'm experiencing the same problems using Apache 2.0.49 with RedHat Linux 8.0 (same backtrace, ...). So far I've been able to track it down to the PCRE extension. When I add "--without-pcre" everything is fine. I've now replaced "ext/pcre", using the version from PHP 4.3.4 (PCRE 4.3) and the problem is gone. My suspicion is that the new PCRE version has memory allocation problems. ------------------------------------------------------------------------ [2004-03-29 10:45:53] [EMAIL PROTECTED] read above comment. ------------------------------------------------------------------------ [2004-03-29 10:45:38] [EMAIL PROTECTED] Sorry, but your problem does not imply a bug in PHP itself. For a list of more appropriate places to ask for help using PHP, please visit http://www.php.net/support.php as this bug system is not the appropriate forum for asking support questions. Thank you for your interest in PHP. The backtrace shows the crash to reside deep inside AP2 code and not in PHP, hence this is not a PHP bug. ------------------------------------------------------------------------ [2004-03-29 05:25:01] as at netoholic dot de my backtrace: (gdb) bt #0 0x4b8f2630 in ?? () #1 0x080728a1 in regex_cleanup (preg=0x0) at util.c:258 #2 0x4b56c39d in run_cleanups (cref=0x80ac838) at apr_pools.c:1951 #3 0x4b56bbe9 in apr_pool_clear (pool=0x80ac828) at apr_pools.c:693 #4 0x0806e4d2 in main (argc=4, argv=0xb1d38f34) at main.c:574 #5 0x4b6558ae in __libc_start_main () from /lib/libc.so.6 apache built with prefork mpm... ------------------------------------------------------------------------ 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/27735 -- Edit this bug report at http://bugs.php.net/?id=27735&edit=1
