Sorry, didn't meant to flame, I just tryed for hours to make it work with no results, and was a little frustrated.
Before I posted the previous message I didn't know that I could run dbg-cli whith the "run" command (my fault). I only tried the "listening" one. I made it work with the first command, but not with the second.
I was checking 7869 port because, when I did "netstat -naop|grep dbg-cli", when dbg-cli is running "listen" command I got somthing like this:
$ netstat -naop|grep dbg-cli
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp 0 0 0.0.0.0:33752 0.0.0.0:* LISTEN 7302/dbg-cli off (0.00/0/0)
It says that dbg-cli is listenning on 33752 port, although the "show port" says 10001. When in my url I added "?DBGSESSID=1@localhost:33752" I got this:
DBG
Failed to start debug session
reason:
failed to establish connection to client host on localhost:7869
thats why I assumed it looked for the server on 7869.
Any idea of why it behaves like that?
Should I tell apache to listen on 10001 port?