Bug #14529 Updated: script doesn't always finish output

ID: 14529 Updated by: warrenp@mountaincable.net -Reported By: jay1@swift-web.com +Reported By: warrenp@mountaincable.net Status: Open Bug Type: Output Control Operating System: Linux RH 7.2 PHP Version: 4.1.1 New Comment: I think i had something similar happen to me. It would just stop printing to the screen and either spit out crazy characters or stop altogether. I commented out every line and brought it back one by one until i located the problem. Although i'm still not exactly sure what's going on I might have a solution. (worked in my case) I put a flush() every now and then. It seemed to fix the problem. Previous Comments: ------------------------------------------------------------------------ [2002-02-15 20:23:31] jay1@swift-web.com I've followed the instructions on the gdb backtrace page but I can not find a core file anywhere on the site. When I tried running httpd -X in the gdb itself I can not access the page. I'm using RedHat 7.2 on my test server. I ran the command (to test it) /usr/sbin/httpd -X and it starts fine and no prompt comes back (which I think is normal). The moment I open a webpage it returns the line: Segmentation fault and then goes back to the command prompt. So this would tell me I found the right command line to run but when I try: gdb /usr/sbin/httpd run -X (from inside the gdb prompt) it says starting new thread and then locks up. If I try opening a web page it comes up as not found (just like it does when the httpd server is not running at all). Any tips on what I'm doing wrong. At least I've finally confirmed it is PHP crashing. I've tried compiling with various options enabled or disabled. I've got the --enable-debug take and I did not set the --enable-trans-sid this time. Thanks ------------------------------------------------------------------------ [2002-02-05 20:37:39] yohgaki@php.net To properly diagnose this bug, 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". ------------------------------------------------------------------------ [2002-02-05 18:55:06] jay1@swift-web.com When I use simple little scripts it seems to work fine. The pages where I have problems is where there are dynamically called include_once and variable variables used. For me the output seemed to work at first with output.buffering on but it turns out there was problems on other pages then (that weren't bothered by it being off). And IE6 would simply load pages from cache of old pages (and Netscape would simply crash with a connection lost error) I also discovered that some environmental variables working with sessions would fail to if there was a tiny error on html output at least in one consistent test. Example: If I had page (such as index.php) generate a basic HTML page but within the html code generated there was an <img> tag with an image name that did not exist on the server anymore (I had renamed it and forgot to update that script). The browser just shows standard little box with x in it where image should be as usual. When this was happening, if I echoed the value of $HTTP_SERVER_VARS['PHP_SELF'] it would return index.php (or the name of the page). However, if I saved that value to a session, then even though a test before the script end showed it correctly set, upon reloading it would be set to the page name (image.gif). I have tried the compiling with AND without --enable-trans-sid and these errors still continue with no change. I have to keep my production server on php 4.0.6 as it simply is way to unreliable in 4.1.0 or newer (including 4.2.2-dev). I use a lot of serialize/unserialize and really was hoping to upgrade for the performance differences. ------------------------------------------------------------------------ [2002-02-05 18:38:03] yohgaki@php.net And what happens when you get rid of --enable-trans-sid from your confiugre line? ------------------------------------------------------------------------ [2002-02-05 18:36:38] yohgaki@php.net Anyone have short complete script for this bug? ------------------------------------------------------------------------ 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/14529 -- Edit this bug report at http://bugs.php.net/?id=14529&edit=1