This is really an impressive product: it is capable of doing the exact same thing under a wide range of circumstances. If that one thing were useful, it would be really great.

So, yes, I downloaded and rebuilt PHP so it was "cgi" instead of "cli":

The dumpinfo under 5.2 isn't as helpful as the one under 5.1 but it looks like it's reading the same ini file.
Needless to say, I got the same behavior from DBG:


Are you actually suggesting that since I cannot run DBG in the simplest, easiest case, I should purchase a product in the hope that it will run in a networked, multi-server case? Until we can successfully evaluate DBG, we aren't purchasing anything based on it.

Seems you forgot to install debugger otherwise this message would shouw its version.


How can you blame the product if you even did not install it ?

Not forgot, but apparently the new version of PHP doesn't read the same php.ini by default. So I did this:

And it said "PHP Warning: PHP Startup: dbg: Unable to initialize module".

Which makes sense! This is the 5.2 PHP and I had install the 5.1 debugger. Finally, an error message I can understand. So I also installed the 5.2 debugger, made a local copy of the php.ini file, and. pointed that one to the 5.2 installation.

Well, just guess what I got next.


It isn't as funny when all your jokes have the same punchline.[/quote]

it's the most expected because still you did not provide path to your php.ini, therefore it was not found, and dbg was not loaded.
There are three ways that will let you get your php.ini found by php:
-copy php.ini to the location where php searches for this file (PREFIX/lib by default). You may want to run phpinfo() to see the location on the top.
-re-run configure for php with --with-config-file-path=/etc command line argument, then make clean, make, and finally make install
-run dbg-cli with environemnt that contains PHPRC variable pointing to php.ini file, for example: PHPRC=/etc/php.ini ./dbg-cli

I recompiled the php so it would load custom php.ini (and hence the debugging module) without any additional parameters).

I'll just let our studio audience guess what happened next.

I bet you got it working.