#45987 [Opn->Fbk]: Problem in paths that have backslashes

ID: 45987 Updated by: pajoye@php.net Reported By: masiena at hotmail dot com -Status: Open +Status: Feedback Bug Type: Scripting Engine problem Operating System: Windows Server 2003 PHP Version: 5.3CVS-2008-09-03 (snap) New Comment: Try without the double quotes in php.ini or use / as path separator. \x is used as special characters in double quotes string, nothing new here. \t is a tab, \n a new line, etc. Previous Comments: ------------------------------------------------------------------------ [2008-09-03 19:54:17] masiena at hotmail dot com Description: ------------ On Windows, directives that have backslashes (\) in file paths are broken. When something like \t is seen (like in error_log="c:\temp\err.log"), it's interpreted like a control sequence (in the example, a tab), and no error logs are generated. This behavior is present in many directives relative to file paths. Solution (temporary?): use forward slashes instead (even in Windows). The same is valid for PHP 6. This is a PATH problem because, where error_log=syslog is used, the messages are correctly sent to Event Viewer. Another clue: phpinfo() output "eats" \t. Reproduce code: --------------- In PHP.INI: error_log = "D:\Progs\php\temp\Logs\php5.3_error_log.txt" include_path = ".;D:\Progs\php\include" etc. Expected result: ---------------- No error logs are generated. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=45987&edit=1