I. COMPILING & INSTALLING

I believe that the process is quite simple. 
Just run the following commands:

./configure
make 
make install

If it fails during this process, you'd check if the following packages are
installed:

gcc 2.96 or higher
glibc 2.2 or higher

readline
readline-devel
ncurses
ncurses-devel

If ncurses is not available under your platform you may try termcap, Hcurses
and alternative libraries. First check readline dependencies.

If configure fails to run, you may try to rebuild it using buildconf script.
In this case you'll need:
automake 1.4p5 or higher
autoconf 2.13 or higher

By default dbg-cli executable is installed into /usr/local/bin/ 
dbgbaselib.a and necessary headers in /usr/local/lib and /usr/local/include
respectively. if you don't want dbg to be installed in /usr/local/ 
please supply --prefix argument to configure.


II. RUNNING

Starting with 2.11.32 I added support for initialization file ~/.dbgcli_init
where you can enter the commands to be run each time you start dbg-cli.
You may want to have there command such as set mode on, set mapurlroot 
http://localhost/ etc.
Command line arguments supperceed the commands from the initialization file
as they have effect after the commands ran.
Run dbg-cli --help to see the command list arguments supported.


III. INTERFACE

After you ran dbg-cli, you may want to open a script and step though it

dbg>file myfile.php
dbg>run
dbg>step

If you want to debug your script under an Apache (or any other php-enabled WEB) 
you should use the following commands:

set mode -- Set HTTP mode of debugging.
set mapurlroot -- Set URL root for mapping.
set maplocalroot -- Set local root for mapping.
set mapremoteroot -- Set remote root for mapping.

For example:
>set mode on
>set mapurlroot http://localhost/
>set mapremoteroot /usr/local/apache/htdocs/
>set maplocalroot /usr/local/apache/htdocs/
>file /usr/local/apache/htdocs/myfile.php
>run
>break /usr/local/apache/htdocs/myfile.php:12
>cont

Alternatively, you may want to turn dbg-cli to listening mode by running 
listen command, then launch your favorite web browser and enter an URL with
DBGSESSID argument, for example
http://myhost/mydir/myscript.php?DBGSESSID=1@clienthost:7869
(I presume you issued port 7869 command before)
listen accepts one argument - number of seconds to wait.



IV. TROUBLESHOOTING

If you got "session startup timeout expired" you'd first check if dbg.so 
extension is added to php.ini as follows:

####################################
extension=dbg.so
[debugger]
debugger.enabled=On
debugger.profiler_enabled=On
####################################

also, some people reported that even with settings shown above dbg-cli still
times out. In this case please make sure php finds its php.ini. See php 
documention on how it searches for php.ini

You may also want to check phpinfo() to see if DBG is loaded correctly and 
enabled. Take care, dbg.so is version depended and therefore you'd install 
dbg.so compatible with php installed in your system.

I tested dbg-cli under RedHat 7.2, RedHat 7.3, RedHat 9, Mandrake 9.1, 
Fedora Core 2, FreeBSD 4.10, SuSe 9.3 and SuSe 10.


V. FEEDBACK

You can post your comments at NuSphere public forum board:
http://support.nusphere.com/


Enjoy.
