I've spent all day now reading forum posts and trying to get debugging working with the 3.2.2 eval.

When trying to use a 3rd party browser the most frequent error message is

Failed to run DBG session
reason:
client ip address [NULL] lookup failed
debugger request found in "query_string".
Not sure what it means? Visit http://www.nusphere.com/dbg/ for troubleshooting.

depending on the hosts_allow line in php.ini, and is also shown trying to browse any other localhost/.php file, unless the cookie it leaves behind is killed:

Name:DBGSESSID
Content:382196511796600006%3Bd%3D1%2Cp%3D0
Host:localhost
Path:/

php.ini settings:

[debugger]
debugger.enabled=on
debugger.profiler_enabled=on
debugger.hosts_allow=localhost (and oher variations incl. 127.0.0.1)
debugger.hosts_deny=ALL
debugger.ports=7869, 10000/16

machine and servers
suse 9.0
php-4.3.3
apache 2.0.47

from phpinfo:
This program makes use of the Zend Scripting Language Engine:
Zend Engine v1.3.0, Copyright (c) 1998-2003 Zend Technologies with DBG v2.16.12, (C) 2000,2004, by Dmitri Dmitrienko

DBG php debugger, version 2.16.12, Copyright 2001, 2004 Dmitri Dmitrienko, http://www.nusphere.com/dbg

Version 2.16.12
Linked as a shared library.
Dbg security enabled.
Profiler compiled, enabled

Directive Local Value Master Value
debugger.enable_session_cookie On On
debugger.enabled On On
debugger.fail_silently On On
debugger.hosts_allow protected value protected value
debugger.hosts_deny protected value protected value
debugger.ignore_nops Off Off
debugger.JIT_enabled Off Off
debugger.JIT_host clienthost clienthost
debugger.JIT_level 3 3
debugger.JIT_port 7869 7869
debugger.net.chunksize 128000 128000
debugger.net.maxpacketsize 1024000 1024000
debugger.ports protected value protected value
debugger.profiler_enabled On On
debugger.session_nocache On On
debugger.timeout_seconds 300 300

Ayway, I gave up and tried using the built-in server, but got this amusing message:

"PhpED is not currently configured to handle files with ".php" extension. Check that this extension is associated with PHP interpreter."

OK, I give up, if PhpED doesn't know it's own name I'll be glad to type it in but what is the name of the Linux PhpED php file handler excutable? I'd try everything that looks execuable under /opt/phped but I'm just too tired of it today.

3.2.2 ? Do you mean you're trying to run Linux version of PHPED ? In this case forget about dbg 2.16 and install debugger modules that come with phped 3.2.2.

"...forget about dbg 2.16 and install debugger modules that come with phped 3.2.2."

????

I'm using the copy of dbg.s0-4.3.3 which came with phped 3.2.2 , as per instructions (to match php 4.3.3).

PHPED 3.2.2 comes with 2.14, not with 2.16.
You have to install dbg-2.14 if you want to work with phped 3.2.2/Linux.

Ok, I'm willing to give it a fair shot.

I uninstalled, then went through and wiped out all remaining traces of phped including every dbg.s0-x.x.x and reference to same, and , just to be sure, wiped and reinstalled apache2 with php4, then did a fresh install of phped 3.2.2 for Linux, setting up for debugging per instructions. I actually rebooted between installs, just in case something was left running that might keep dbg in memory.

After all that, phpinfo tells me the debug version is dbg-2.16.12. YOU may think phped 3.2.2 comes with dbg-2.14, but the software is apparently unimpressed with your opinion. BTW, it still doesn't work.

then you installed phped-3.3.2, not 3.2.2 as you stated before.
If it fails to start debug take a look at
a) run mode you have set. It should be HTTP/3rd party web server
b) in the project settings you should specify htdocs for both remote root directory and project root directory
c) in root url you have to specify http://localhost/

that's all tricks so far...

Ok, I think I have it now, maybe.
dbg.so-4.3.3 is incompatible with dbg.so-4.3.3 (couldn't use better names?) so use the library from PhpEd 3.2.2 with PhpEd 3.3.2 . That got rid of thebut now I get a "Failed to start debugging session" errorbox.

HTTP/3rd party web server is set
htdocs is spec'd for remote root and project root.
Root URL is http://localhost/
In php.ini:
extension=dbg.so-4.3.3
[debugger]
debugger.enabled=on
debugger.profiler_enabled=on
debugger.hosts_allow=ALL
;debugger.hosts_deny=ALL
debugger.ports=7869, 10000/16

4.3.3 is not the dbg version. Otherwise it would be dbg-4.3.3.so
4.3.3 is php version the dbg.so is compatible with.

Phped 3.2.x comes with dbg.so version 2.14 while phped 3.3.x comes with 2.16. Latter is backward compatible with 2.14 while 2.14 can't work with 2.16's requests when client address is empty (NULL). That's the matter of the message you got.

If you got TIMEOUT error please proceed with these instructions:
tip-troubleshooting-debugger-communications-t579.html#2264

??? I should use dbg-4.3.3.so instead of dbg.so-4.3.3? Where is that located?

Our story thus far:
PhpED 3.3.2 Build 3386eval (?-can't read that tiny type on my monitor).
With DBG V2.16.12 (dbg.so-4.3.3 that comes with PhpEd 3.3.2 eval)
pages don't open and I get the errorWith DBG V2.14.10 (dbg.so-4.3.3 that comes with PhpEd 3.2.2 eval)
pages will open but I get the errorOther settings still as in previous posts.

One change: I went back and tried PhpEd 3.2.2 one more time but couldn't get the debugger working there, either.

No, I did not say that. What I said is that you have to make sure that you use appropriate dbg module. So if you run php 4.3.3 you'd use dbg.so-4.3.3 module. Module itself should be taken from the debugger subdirectory of phped, nowhere else.
If the problem still persists please run phpinfo() and post all the results here.