brashquido:
Running PHP at the command line is more or less the same as configuring logging. Basically it just gives you a much clearer insight into what your PHP processes are actually doing. The only issue with using PHP cli is that it takes IIS out of the loop, so if you have an IIS configuration issue with PHP using the cli will not help.
true, but its also eliminates or (in my case) confirms php-cgi is having the problem
I currently have a issue where php runs, log file is set, no error output, but php is crashing halfway through a page. I isolated the problem down to a certain line, but there is nothing wrong with that line.
By default I have the php dev ini, so it was set to E_ALL | E_STRICT. If I change it to E_STRICT, then php will execute more lines before crashing (or freezing, giving a 500.0). The default ini has 128M, and the code is in the middle of maybe a 50-100 SQL CREATE ststements.
My question here is: are there memory size issue (running out of allocated memory) with PHP, SQLite, and/or MySQL. (the current SQL statements are being piped through SQLite, I do not have a x64 install of MySQL, or a MS SQL server, to compare execution to..)
Or: is there (also) a memory limit issue within IIS7 when dealing with FastCGI
note: I can get the SQL statements to execute when I cut and paste into another page, but only if I set E_STRICT (not E_ALL)
Paul