ID: 41280 Comment by: dayseye at 21cn dot com Reported By: wimroffel at planet dot nl Status: Feedback Bug Type: Filesystem function related Operating System: Windows XP PHP Version: 5.2.2 New Comment:
I guess it's a internal charset problem. does Borland C handle ANSI/UTF-8 in the same way both in WinME and WinXP? If not, you must check the text file what charset it's using. Previous Comments: ------------------------------------------------------------------------ [2007-05-04 19:56:27] [EMAIL PROTECTED] >Yes. The data is echoed to the screen. And as it is text with >some html changes are often immediately visible. What kind of changes? Where can I see them? >>It looks like there is some memory leak. >When the data that is echoed on the screen is incorrect usually one >or a few bytes are incorrect. However, once I saw a part of a >variable list like you see sometimes when you look at an exe file >in a text editor. Well, I'm afraid it has nothing to do with memory leaks. ------------------------------------------------------------------------ [2007-05-04 18:59:35] wimroffel at planet dot nl > Well, then there are no crashes and you are wrong. I don't know what a crash looks like and whether what I see is a crash. I don't know whether I installed MSVC correctly. But I do know that the software is behaving in a wrong way. >>What I did find find in other experiments was that even when all >>output is echoed at once the data is sometimes read incorrectly. >"Incorrectly"? How did you compare the data? Looking on the screen? Yes. The data is echoed to the screen. And as it is text with some html changes are often immediately visible. >>It looks like there is some memory leak. >What are you talking about? When the data that is echoed on the screen is incorrect usually one or a few bytes are incorrect. However, once I saw a part of a variable list like you see sometimes when you look at an exe file in a text editor. I have spent years developping software myself - in Borland C. That is years ago. But I know what I am talking about. I developped a PHP/MySql application under Windows ME. Now I am trying to port it to XP, but this bug is making it impossible. The bug is still there when I remove the MySql part. And it is no longer there when I save the page as HTML. So I have to conclude that it is PHP. ------------------------------------------------------------------------ [2007-05-04 13:19:24] [EMAIL PROTECTED] >And then it stopped for me. I am unaware when PHP crashes and >I never see a cancel button that I could press. Well, then there are no crashes and you are wrong. >What I did find find in other experiments was that even when all >output is echoed at once the data is sometimes read incorrectly. "Incorrectly"? How did you compare the data? Looking on the screen? >It looks like there is some memory leak. What are you talking about? ------------------------------------------------------------------------ [2007-05-04 13:09:38] wimroffel at planet dot nl I am not familiar with those debugging procedures. I tried, but I see no result. I installed MSVC6 (still had it lying somewhere from MSDN). I downloaded the debug-pack and unpacked it. I copied the files (they are all .pdb files) to both the php and php/extensions directory. And then it stopped for me. I am unaware when PHP crashes and I never see a cancel button that I could press. What I did find find in other experiments was that even when all output is echoed at once the data is sometimes read incorrectly. It looks like there is some memory leak. I tested it on two XP computers with very different setups and hardware. ------------------------------------------------------------------------ [2007-05-04 10:31:44] [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 for *NIX and http://bugs.php.net/bugs-generating-backtrace-win32.php for Win32 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. ------------------------------------------------------------------------ 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/41280 -- Edit this bug report at http://bugs.php.net/?id=41280&edit=1
