I couldn't get dbg-cli to work in cgi mode and I traced it to the php interpreter dying prematurely, when the input pipe is closed. I did an experiment with a little shell script (below) which sets the same enviornment as dbg-cli provides and execs php. Sure enough, if the input is closed or is /dev/null, php exists immediately. What is supposed to be going on here?


env -i "PATH=.:/home/sibyl/users/ian/bin:/home/sibyl/users/ian/bin.sibyl:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/usr/local/freemarket/bin:/usr/java/j2sdk1.4.2_01/bin:/usr/local/sbin:/sbin:/usr/sbin" \
"REDIRECT_QUERY_STRING=" "REDIRECT_STATUS=200" \
"REDIRECT_URL=/usr1/home/sibyl/users/ian/public_html/test.php" \
"SERVER_SOFTWARE=DBG/2.1" "SERVER_NAME=localhost" \
"SERVER_ADDR=127.0.0.1" "SERVER_PORT=80" \
"REMOTE_ADDR=127.0.0.1" "SCRIPT_FILENAME=php" \
"GATEWAY_INTERFACE=CGI/1.1" "SERVER_PROTOCOL=HTTP/1.1" \
"REQUEST_METHOD=GET" "QUERY_STRING=" \
"REQUEST_URI=/usr1/home/sibyl/users/ian/public_html/test.php" \
"PATH_INFO=/usr1/home/sibyl/users/ian/public_html/test.php" \
"PATH_TRANSLATED=/usr1/home/sibyl/users/ian/public_html/test.php" \
"HTTP_COOKIE=DBGSESSID=10868692739117560004@clienthost:10001" /usr/bin/php < /dev/null

hmm, why do you think dbg-cli causes php to stop ?
I believe there is another problem.

Ah. Problem solved. PhP builds three things of interest, the apache module, a CGI executable and a CLI executable. I had installed the CLI executable. With the CGI executable this problem goes away