| 
        php.net | support | documentation | report a bug | advanced search | search howto | statistics | random bug | login | 
 PatchesPull RequestsHistoryAllCommentsChangesGit/SVN commits             
             [2014-10-24 09:24 UTC] php at sanexeh dot nl
  [2014-12-04 08:48 UTC] ab@php.net
 
-Status:      Open
+Status:      Closed
-Assigned To:
+Assigned To: ab
  [2014-12-04 08:48 UTC] ab@php.net
  | 
    |||||||||||||||||||||||||||
            
                 
                Copyright © 2001-2025 The PHP GroupAll rights reserved.  | 
        Last updated: Tue Nov 04 14:00:01 2025 UTC | 
Description: ------------ On Microsoft Windows OS there is currently too few information written to the Windows Event Logs (Application, Event Viewer) to be able to figure out where a problem occurs, if one occurs. Test script: --------------- 1, via CLI: c:\php5.5\php-cgi.exe -d a=b -d foo=1() 2, visiting a website running in IIS, when the website has a user_ini.filename file with the following erroneous content: foo = 1() Expected result: ---------------- I don't really care about the actual output format written to Windows Application Event Logs, but it'd be useful to have the started process with commandline arguments: 1: Application popup: PHP Error : syntax error, unexpected '(' in Unknown on line 2 (c:\php5.5\php-cgi.exe -d a=b -d foo=1()) 2: Application popup: : (c:\website\docroot\.user.ini) or 2: Application popup: : (c:\php5.5\php-fcgi-5-5.exe -d a=b) or 2: Application popup: : (c:\php5.5\php-fcgi-5-5.exe -d a=b, c:\website\docroot\.user.ini) Actual result: -------------- 1: Application popup: PHP Error : syntax error, unexpected '(' in Unknown on line 2 2: Application popup: :