ID: 28029 Updated by: [EMAIL PROTECTED] Reported By: coadmin at hostings dot pl -Status: Open +Status: Feedback Bug Type: URL related Operating System: FreeBSD 4.9 and 5.2.1 PHP Version: 4CVS-2004-04-16 (stable) New Comment:
When compiling PHP without debug do you export your own CFLAGS? It is possible that with debug your compiler over optimizes and consequently breaks the code. If you are not setting any optimization options, try doing export CFLAGS=-O before running configure/make/make install procedure. Previous Comments: ------------------------------------------------------------------------ [2004-04-21 15:30:27] coadmin at hostings dot pl Heh, the problem is *strange*... As you reqested, I decided to compile PHP with --enable-debug. All problems went away... The aren't any segfaults and php stream releated functions works correctly all the time. When I compile PHP again, without debug, it reproduces errors quickly... I tried PHP-4.3.3 and 4.3.7dev - both of them works preety good with --enable-debug, and reproduce erros in not debug mode. What's it? Other configure options are the same. In --enable-debug only Zend doesn't work, but my scripts doesn't use it. Please help. I don't know gow to reproduce errors with --enable-debug. ------------------------------------------------------------------------ [2004-04-21 09:29:27] [EMAIL PROTECTED] 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 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. We really need a backtrace. ------------------------------------------------------------------------ [2004-04-21 07:51:08] coadmin at hostings dot pl Latest stable PHP from CVS wasn't helpful for me, but is difference... Apr 21 01:48:37 gw kernel: pid 44845 (httpd), uid 65534: exited on signal 11 Apr 21 01:48:37 gw kernel: pid 45103 (httpd), uid 65534: exited on signal 11 Apr 21 01:48:38 gw kernel: pid 45391 (httpd), uid 65534: exited on signal 11 Apr 21 02:00:20 gw kernel: pid 70302 (httpd), uid 65534: exited on signal 11 Apr 21 02:13:17 gw kernel: pid 91837 (httpd), uid 65534: exited on signal 11 Apr 21 02:13:17 gw kernel: pid 80739 (httpd), uid 65534: exited on signal 11 Apr 21 02:13:18 gw kernel: pid 79870 (httpd), uid 65534: exited on signal 11 Apr 21 02:13:18 gw kernel: pid 79954 (httpd), uid 65534: exited on signal 11 Apr 21 02:13:19 gw kernel: pid 80397 (httpd), uid 65534: exited on signal 11 Apr 21 02:13:19 gw kernel: pid 92146 (httpd), uid 65534: exited on signal 11 Apr 21 02:13:19 gw kernel: pid 80029 (httpd), uid 65534: exited on signal 11 Apr 21 02:13:20 gw kernel: pid 91777 (httpd), uid 65534: exited on signal 11 Apr 21 02:13:20 gw kernel: pid 80190 (httpd), uid 65534: exited on signal 11 Apr 21 02:13:21 gw kernel: pid 80104 (httpd), uid 65534: exited on signal 11 Apr 21 02:13:21 gw kernel: pid 92057 (httpd), uid 65534: exited on signal 11 I can't do GDB because there are child processes, not root, and also I haven't httpd.core. Now I can't see "HTTP request failed!" but document contains no data. (unexpected network error in lynx). ------------------------------------------------------------------------ [2004-04-20 20:42:35] [EMAIL PROTECTED] Please try using this CVS snapshot: http://snaps.php.net/php4-STABLE-latest.tar.gz For Windows: http://snaps.php.net/win32/php4-win32-STABLE-latest.zip ------------------------------------------------------------------------ [2004-04-20 11:41:04] servers at apandres dot com I have the same problem, php 4.3.3 on redhat. i am checking for a reciprocal link of a submitted page. it is working for a few hours and then nothing can be submitted any more. same error msg. after apache restart everything is ok again for the next few hours. i did not notice this in php 4.3.2 ------------------------------------------------------------------------ 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/28029 -- Edit this bug report at http://bugs.php.net/?id=28029&edit=1
