ID: 27820 Updated by: [EMAIL PROTECTED] Reported By: brandonnimon at comcast dot net -Status: Feedback +Status: No Feedback Bug Type: Reproducible crash Operating System: Windows (xp and 2000) PHP Version: 4.3.7 New Comment:
No feedback was provided for this bug for over a week, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open". Previous Comments: ------------------------------------------------------------------------ [2004-12-13 00:12:01] [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-06-16 08:28:58] brandonnimon at comcast dot net After complicating my code moreso since the 4.3.6 release, I have run into the bug a few more times in the same type of format as before. The 4.3.6 release seemed to make it more reliable and forgiving, but only to a point. And I've been finding myself spending way more time than I should trying to write "Windows Compatable" code, which should work fine for everyone. But I run into a lot of code that halts on Windows servers, and not on Linux servers (most of the Linux servers have 4.3.4). ------------------------------------------------------------------------ [2004-04-01 01:57:20] brandonnimon at comcast dot net Description: ------------ When programming on complicated sites, I have run into a problem a few times. I'll add some code (sometimes it could be something as simple as a few lines like this: echo "<table><tr><td>Table 1</td></tr>"; But seems to better replicated with large complex arrays, just 'cause they are larger, there is a greater chance. When I have run into this problem, I transfer my code to my Linux machine, and a Unix webhosting server. They all do the same thing. I've also had it stop in the middle of a php function such as print_r(). It will suddenly just stop. I've seen it print_r($array); and stop like this: Array ( [0] => Array ( [user] => admin [0] => Array ( [album] => 1 [0] => Array ( [date] => 1080354398 [name] => 105blaster_s9969041.jpg [number] => 0 ) [1] => Array ( [date] => 1080460914 [name] => ballot7784410.jpg [num ..just stops in the middle of the dump. Also, every time a page like this is opened, an execution of php.exe is started. And after 30 or so open there is an "internal server error". I'm not sure of how the PHP client works, but my guess is that php.exe is crashing partially, and it tries to start another, and I just end up with a bunch of the same program. I also think it may have something to do with error reporting. Because to a point, I was able to supress the bug by adding @ signs to certain lines of code, ones which could potentially return an error but don't (I did this just as some debugging attempts, and was suprised that it worked -- but I could only do it to so many relevent lines before I ran out, and the problem persisted after I added something else). And I checked my apache error log and no "Segmentation Fault" errors are in there. Currently I am using a GD2 extension, but I have run into the problem when I was using all default settings. Reproduce code: --------------- I can't seem to reproduce the error on Linux with this code, but I know with some other code I have. I don't know exactly what part is causeing it, so I am using all of it. If you see some inconsistancies, it is probably because I was trying to debug. http://24.127.21.245/prod_error/source.zip Expected result: ---------------- The page to be displayed fully. And no php.exe's to start. Actual result: -------------- Currently the output is stopping for no apearent reason (see description for an example). The output will just stop at some character, and the browser continually tries to get the rest. Everytime a page like this is opened, an execution of php.exe is started. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=27820&edit=1
