So from that log, all I can tell is that xdebug established a socket
with something. It sent the initial handshake. If PDT was communicating
with xdebug it would be sending commands to configure the debug env but
the log doesn't show this.
One possibility (if in fact it is communicating with PDT) is that PDT is
rejecting the socket. Have you got remote session initiation turned on
and you are trying to debug that way or are you creating a Web script
Check you have xdebug installed in the correct manner for the version
and type of php you are using (check http://www.xdebug.org) for more info.
On 28/09/2010 17:08, email@example.com wrote:
> Hi, i've recently upgraded to PDT 2.2.0 ( helios win32 version) and have
> not been able to get xdebug working. I had previously been using xdebug
> with PDT 2.1.
> I've done a complete reinstall of PDT 2.2.0 and created a new workspace.
> I've upated xdebug to the latest version of 2.1.0.
> I'm trying to use xdebug with a remote server.
> In the xdebug log I get a message such as this:
> Log opened at 2010-09-28 15:09:23
> -> <init xmlns="urn:debugger_protocol_v1"
> fileuri="file:///test/debug.php" language="PHP" protocol_version="1.0"
> (c) 2002-2010 by Derick Rethans]]></copyright></init>
> -> <response xmlns="urn:debugger_protocol_v1"
> xmlns:xdebug="http://xdebug.org/dbgp/xdebug" status="stopping"
> Log closed at 2010-09-28 15:09:23
> I don't really know what is causing xdebug to stop. Does anyone have any
> suggestions. I've tried changing the port several times in case there is
> a conflict but it doesn't seem to make any difference.
Hi Dave, I couldn't tell much from that log either!
I was initiating a remote debug request from Firefox using the XDebug extension. The log at least told me that it had got the right file to debug, although the reason for stopping doesn't give much away.
Your prompt made me check my PDT options again, and sure enough I had "Accept remote session (JIT)" set to "off" instead of the required "any". With this changed it now seems to work fine.
Thanks for the suggestion, it helped me fix the problem.