Can't debug remote project

Posted August 6th, 2008 by Suggs

Hi there,

I've currently got a remote project and have installed xdebug on the server but when i go to start i get the error

"Missing debug information in the registry. Can not start debug session"

and in the output it says "The project does not have a deployment settings configured"

Can anyone help me out please? I can only deploy without debugging and that's just useless to me.

Thanks in advance

‹ Vistas Program Compatibility Assistant Unhandled win32 exception ocurred in vsphp_dbg.exe[10472] ›

Comments

    What version of VS.Php are

    On August 6th, 2008 webmaster said:

    What version of VS.Php are you using? Have you considered reinstalling the software?

    Also are you running as admin?

    I've re-installed VS.php 2.5

    On August 7th, 2008 Suggs said:

    I've re-installed VS.php 2.5 now. Now it executes and loads the page but fails to hit any breakpoints.

    I've set the port to 9000 and as I said xdebug seems to be set up fine on the server but simply no debug return.

    Any ideas?

    Did you change the port

    On August 7th, 2008 webmaster said:

    Did you change the port number in VS.Php to listen on port 9000?

    If so, the next thing is to enable the remote_log on xdebug to see what's going on.

    Yes I've changed Vs.php to

    On August 8th, 2008 Suggs said:

    Yes I've changed Vs.php to listen on 9000. I've already enabled logging on xdebug as well

    This is my php.ini entries for xdebug:

    zend_extension="/usr/lib/php/modules/xdebug.so"

    xdebug.remote_enable = 1
    xdebug.remote_host = 62.**.**.**
    xdebug.remote_port = 9000
    xdebug.remote_mode = req
    xdebug.remote_handler = dbgp
    xdebug.remote_log="/home/ggarrett/log.txt"

    Is there anything wrong with those settings?

    This is a snip of the log file

    Log opened at 2008-08-08 09:53:47
    ->

    <- feature_get -i transaction_id -n supports_async
    ->

    <- feature_get -i transaction_id -n notify_ok
    ->

    <- stdout -i 3 -c 1
    ->

    <- stderr -i 4 -c 1
    ->

    <- breakpoint_set -t exception -x "Fatal error" -i 5
    ->

    <- breakpoint_set -t exception -x "Parse error" -i 6
    ->

    <- breakpoint_set -t exception -x "Unknown error" -i 7
    ->

    <- breakpoint_set -i 8 -t line -f file:///var/www/sites/dev/htdocs/files/test.php -n 3 -r 0
    ->

    .

    Ok, so the problem is

    On August 8th, 2008 webmaster said:

    Ok, so the problem is mapping files from the remote location to the local machine. Could you post the first message from the log? it has a path in it. This path is used to do the mapping to the local machine.

    Sure can Here it is: <init

    On August 8th, 2008 Suggs said:

    Sure can

    Here it is:

    <init xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" fileuri="file:///var/www/sites/dev/htdocs/files/test.php" language="PHP" protocol_version="1.0" appid="9014" idekey="2"><engine version="2.0.3"><![CDATA[Xdebug]]></engine><author><![CDATA[Derick Rethans]]></author><url><![CDATA[http://xdebug.org]]></url><copyright><![CDATA[Copyright (c) 2002-2008 by Derick Rethans]]></copyright></init>

    Incidentally, in the meantime I've managed to get DBG working so at least the connectivity between client/server is all correct.

    What is the start

    On August 8th, 2008 webmaster said:

    What is the start url?

    http://[your server]/files/test.php

    Thanks

    Yes that's correct The url

    On August 8th, 2008 Suggs said:

    Yes that's correct

    The url is http://"servername"/files/test.php

    I'm going to send you a

    On August 9th, 2008 webmaster said:

    I'm going to send you a private build of the debugger that has tracing enabled but I need to know which edition of VS.Php are you currently using?

    I was using 2.5 but in an

    On August 11th, 2008 Suggs said:

    I was using 2.5 but in an attempt to rectify the problem (and lookng through the forum) i downloaded and installed the 2.6 beta.

    I'm happy to change version on your recommendation

    For VS 2005 sorry.

    On August 13th, 2008 Suggs said:

    For VS 2005 sorry.

    *bump*

    On August 14th, 2008 Suggs said:

    *bump*