Some feedback: I tried to get the binaries from http://www.php4win.de/ working but ran in to problems that prevented me getting as far as testing the XML part. I then ran in to problems switching PHP from CGI to module on an NT machine. I updated the machine from Apache 1.3.14 to 1.3.19 and everything worked. The error with PHP module and Apache began when you switched to the new format Win32 install in PHP 4.0.4pl1. The error was something about a missing entry point and was similar to the error reported in error id #8990. By the time I had all that working, I had used some PHP text and array code to read the XML file without using the XML functions. I am writing the PHP code for a customer that will not install things from development sites. The customer always waits for RPMs. I will now have to stay back at the same PHP level as the customer. Perhaps I can dive in to the leading edge again after this project. See you at ApacheCon. Peter Bug Database wrote: > > ID: 8647 > Updated by: sniper > Reported By: [EMAIL PROTECTED] > Old-Status: Feedback > Status: Closed > Bug Type: Reproduceable crash > Assigned To: > Comments: > > No feedback. > > --Jani > > Previous Comments: > --------------------------------------------------------------------------- > > [2001-01-24 19:32:06] [EMAIL PROTECTED] > This (XML related) bug should be fixed in CVS already. Please try the binaries > > found at http://www.php4win.de/ > > --Jani > > --------------------------------------------------------------------------- > > [2001-01-11 15:06:51] [EMAIL PROTECTED] > can you please append some *short* reproducing code? > > i tested file() with a file greater than 100k and it didn't crash. > > --------------------------------------------------------------------------- > > [2001-01-10 21:05:56] [EMAIL PROTECTED] > Loading array via file(). File is 4Mb of text. Bang, PHP died. > > I increased PHP memory from 8 MB to 20 Mb but did not fix it. I cut the file down to >about 10Kb but that did not fix it. When I comment out the line containing file(), >that removes the problem. > > I thought it might not be file(), it might be any part of the code that uses the >array so I commented out file() and inserted statements that manually load the array >with data. The script ran to completion using the manual array. > > gdb backtrace is gobbledygook to me. I am reading your documentation page to see if >any of it is relevant to Windows environment. If your page helps me change my php >setup to produce additional diagnostics, I will add them to this report. > > Apache is the latest Apache 1.14 or something from about 3 weeks ago. PHP is PHP >4.0.4 from the large download file. NT 4.0 SP6a running without a hitch for 6 months. >The code I am working on was working in the middle of last year on a PHP3 downloaded >in the middle of last year. > > --------------------------------------------------------------------------- > > ATTENTION! Do NOT reply to this email! > To reply, use the web interface found at http://bugs.php.net/?id=8647&edit=2 -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
