#22497 [Opn]: php writes on wrong position in file after new lines

ID: 22497 User updated by: henrik dot gebauer at web dot de Reported By: henrik dot gebauer at web dot de Status: Open Bug Type: Apache2 related Operating System: Windows 2000 -PHP Version: 4CVS-2003-03-05 (stable) (Apache2 module) +PHP Version: 4.3.2RC1 New Comment: I could locate the bug in main/streams.c main/php_streams.h by using old versions of those files (PHP 4.3.0) I hope this helps. Previous Comments: ------------------------------------------------------------------------ [2003-03-09 18:40:33] moriyoshi@php.net I'm not sure, but maybe this problem has something to do with _setmode() invocation in the CLI/CGI version. ------------------------------------------------------------------------ [2003-03-05 14:04:10] henrik dot gebauer at web dot de Yes. I tried the CGI version today and all chars were written into the file. ------------------------------------------------------------------------ [2003-03-05 12:34:41] sniper@php.net So the bug happens ONLY under Apache2 when you run PHP as apache module? ------------------------------------------------------------------------ [2003-03-05 07:48:24] henrik dot gebauer at web dot de I have my own php.ini. (changes: max_execution_time=5, error_reporting=E_ALL, include_path, extension_dir, extension=php_gd2.dll, session.save_path=C:\WINNT\TEMP and I have the Zend Optimizer installed) But I tried it also with the php.ini-dist of the latest stable snapshot what didn't fix the bug. Normally, I'm using PHP as an Apache2 module but I couldn't reproduce the bug with CGI/FastCGI. It doesn't matter if I use a compiled snapshot or if I compile it by myself. ------------------------------------------------------------------------ [2003-03-04 19:29:00] sniper@php.net Are you 100% sure there isn't some clash with the versions now?? Also, does this happen with CLI/CGI ? What php.ini are you using? And what have you changed in it? Are you loading any extensions in it? If only you have this problem, and two developers can't reproduce it, it's most likely something wrong in your side, not in PHP.. ------------------------------------------------------------------------ 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/22497 -- Edit this bug report at http://bugs.php.net/?id=22497&edit=1