|
|
|
Re: not suspend when debugging with xdebug [message #524255 is a reply to message #524220] |
Wed, 31 March 2010 05:52 |
Eclipse User |
|
|
|
Originally posted by: dkel50.hotremovemail.com
Ensure xdebug is loaded and configured correctly. run a script with
phpinfo() in it to get the output.
If you are php 5.2 ensure you load xdebug with the appropriate
zend_extension or zend_extension_ts call in php.ini depending on whether
you are using thread safe or non thread safe.
if you are php 5.3 ensure you use just zend_extension.
try using the xdebug calls such as xdebug_break() in your script to see
if that suspends
Dave Kelsey
On 31/03/10 09:24, No way wrote:
> Hi, everybody.
>
> I using PDT 2.1 with all package and Xdebug. Everything seems okay, but
> Eclipse wasn't suspend at break point or first line when I was debugging.
> This is image:
>
>
> Thanks.
|
|
|
Re: not suspend when debugging with xdebug [message #524256 is a reply to message #524220] |
Wed, 31 March 2010 05:52 |
Eclipse User |
|
|
|
Originally posted by: dkel50.hotremovemail.com
Also ensure that zend_optimiser is not enabled, check out the FAQ at
http://www.xdebug.org for more info.
Dave Kelsey
On 31/03/10 09:24, No way wrote:
> Hi, everybody.
>
> I using PDT 2.1 with all package and Xdebug. Everything seems okay, but
> Eclipse wasn't suspend at break point or first line when I was debugging.
> This is image:
>
>
> Thanks.
|
|
|
|
Re: not suspend when debugging with xdebug [message #524538 is a reply to message #524450] |
Thu, 01 April 2010 10:24 |
Eclipse User |
|
|
|
Originally posted by: dkel50.hotremovemail.com
I see you are capturing the log from xdebug could you post that from a
run that fails ?
Cheers
Dave Kelsey
On 01/04/10 03:26, No way wrote:
> thank you, Dave.
>
> I sure Xdebug configured and loaded corectly. This is parametter of
> Xdebug in phpinfo(); and I don't install Zend Optimizer.
>
> this is configure in php.ini
>
> [XDEBUG]
> ;xDebug Configuration starts
> zend_extension_ts =
> " C:\wamp\bin\php\php5.2.11\ext\php_xdebug-2.1.0beta3-5.2-vc6. dll "
>
> xdebug.profiler_output_dir = "c:\wamp\tmp\xdebug"
> xdebug.profiler_output_name = "cachegrind.out.%p"
> xdebug.profiler_enable = 0
> xdebug.profiler_append=0
> xdebug.extended_info=1
> xdebug.remote_enable=true
> xdebug.remote_handler="dbgp"
> xdebug.remote_mode=req
> xdebug.remote_host="localhost"
> xdebug.remote_port=10001
> xdebug.idekey="XDebug"
> xdebug.remote_log="c:\wamp\tmp\xdebug\xdebug_remot.log"
> xdebug.show_exception_trace=0
> xdebug.show_local_vars=1
> xdebug.show_mem_delta=0
> xdebug.trace_format=0
>
> ;xDebug Configuration ends
>
> Xdebug parametters:
>
>
> and error themes:
>
|
|
|
|
Re: not suspend when debugging with xdebug [message #524807 is a reply to message #524717] |
Fri, 02 April 2010 15:23 |
Eclipse User |
|
|
|
Originally posted by: dkel50.hotremovemail.com
Sorry I think you misunderstood. Can you post the output in the log of
you trying to run a web page to debug ?
Dave Kelsey
On 02/04/10 02:50, No way wrote:
> yes, that's right. I created a error when running a web page to see
> error themes of Xdebug.
>
> Eclipse User wrote on Thu, 01 April 2010 06:24
>> Originally posted by: dkel50.hotremovemail.com
>>
>> I see you are capturing the log from xdebug could you post that from a
>> run that fails ?
>>
>> Cheers
>> Dave Kelsey
>> >
>
>
|
|
|
|
Re: not suspend when debugging with xdebug [message #525301 is a reply to message #524863] |
Tue, 06 April 2010 03:28 |
Eclipse User |
|
|
|
Originally posted by: dkel50.hotremovemail.com
The output shows me that PDT is doing everything correctly. I see a
breakpoint being set on line 4 for c:\wamp\www\testdebug\test.php and I
see that is the initial script being executed. I see it doing a step
into which means it should stop at the first line but doesn't. I also
see a value of 3 being output. Could you post your script just in case I
there is something there that may cause the problem.
I don't know why this isn't working. Did you try adding an
xdebug_break(); line into your code and see if that works ? The only
other thing I can suggest is you try the xdebug mailing list and see if
you can get some help there.
Dave Kelsey
On 03/04/10 05:20, No way wrote:
> thank Dave,
>
> this is log of xdebug:
>
> -> <init xmlns="urn:debugger_protocol_v1"
> xmlns:xdebug="http://xdebug.org/dbgp/xdebug"
> fileuri="file:///C:/wamp/www/testdebug/test.php" language="PHP"
> protocol_version="1.0" appid="2104" session="127002765789012"
> idekey="ECLIPSE_DBGP"><engine
> version="2.1.0rc1-dev"><![CDATA[Xdebug]]></engine><author ><![CDATA[Derick Rethans]]></author><url><![CDATA[http://xdebug.org]]></url><copyright><![CDATA[Copyright
> (c) 2002-2010 by Derick Rethans]]></copyright></init>
>
> <- feature_set -i 143 -n show_hidden -v 1
> -> <response xmlns="urn:debugger_protocol_v1"
> xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="feature_set"
> transaction_id="143" feature="show_hidden" success="1"></response>
>
> <- feature_set -i 144 -n max_depth -v 3
> -> <response xmlns="urn:debugger_protocol_v1"
> xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="feature_set"
> transaction_id="144" feature="max_depth" success="1"></response>
>
> <- feature_set -i 145 -n max_children -v 31
> -> <response xmlns="urn:debugger_protocol_v1"
> xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="feature_set"
> transaction_id="145" feature="max_children" success="1"></response>
>
> <- feature_get -i 146 -n encoding
> -> <response xmlns="urn:debugger_protocol_v1"
> xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="feature_get"
> transaction_id="146" feature_name="encoding"
> supported="1"><![CDATA[iso-8859-1]]></response>
>
> <- feature_get -i 147 -n supports_async
> -> <response xmlns="urn:debugger_protocol_v1"
> xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="feature_get"
> transaction_id="147" feature_name="supports_async"
> supported="1"><![CDATA[0]]></response>
>
> <- stdout -i 148 -c 1
> -> <response xmlns="urn:debugger_protocol_v1"
> xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="stdout"
> transaction_id="148" success="1"></response>
>
> <- stderr -i 149 -c 1
> -> <response xmlns="urn:debugger_protocol_v1"
> xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="stderr"
> transaction_id="149" success="0"></response>
>
> <- breakpoint_set -i 150 -t line -f
> file:///C:%5Cwamp%5Cwww%5Ctestdebug%5Ctest.php -n 4
> -> <response xmlns="urn:debugger_protocol_v1"
> xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="breakpoint_set"
> transaction_id="150" id="21040001"></response>
>
> <- step_into -i 151
> -> <stream xmlns="urn:debugger_protocol_v1"
> xmlns:xdebug="http://xdebug.org/dbgp/xdebug" type="stdout"
> encoding="base64"><![CDATA[Mw==]]></stream>
>
> -> <response xmlns="urn:debugger_protocol_v1"
> xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="step_into"
> transaction_id="151" status="stopping" reason="ok"></response>
>
> <- stop -i 152
> -> <response xmlns="urn:debugger_protocol_v1"
> xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="stop"
> transaction_id="152" status="stopped" reason="ok"></response>
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.06063 seconds