Skip to main content

Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Language IDEs » PHP Development Tools (PDT) » xdebug does not stop at breakpoints - hangs at 57% complete
xdebug does not stop at breakpoints - hangs at 57% complete [message #788272] Wed, 01 February 2012 15:39 Go to next message
David Taylor is currently offline David TaylorFriend
Messages: 3
Registered: February 2012
Junior Member
My symptoms are similar to others posted on this and other forums.

xdebug does not stop at breakpoints - hangs at 57% complete.

but the solutions I have tried do not work.


OS: Win 7 x86
Server Config: XAMPP / localhost (
Eclipse: Version 3.7.1 (Indigo)
php: Version 5.38
Apache: Version 2.2.21

php.ini xdebug settings
;zend_extension = "C:\xampp\php\ext\php_xdebug.dll"
zend_extension = C:\xampp\php\ext\php_xdebug-2.1.2-5.3-vc9.dll


xdebug.profiler_append = 0
xdebug.profiler_enable = 0
xdebug.profiler_enable_trigger = 0
xdebug.profiler_output_dir = "C:\xampp\tmp"
xdebug.profiler_output_name = "xdebug_profile.%R::%u"

xdebug.remote_connect_back =1
e script will just continue as if this setting was Off.
xdebug.remote_enable = 1
xdebug.remote_log = "c:\xdebug\log.txt"
xdebug.trace_output_dir = "C:\xampp\tmp"

Log opened at 2012-02-01 14:08:25

<- feature_set -i 11 -n show_hidden -v 1
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="" command="feature_set" transaction_id="11" feature="show_hidden" success="1"></response>

<- feature_set -i 12 -n max_depth -v 3
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="" command="feature_set" transaction_id="12" feature="max_depth" success="1"></response>

<- feature_set -i 13 -n max_children -v 31
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="" command="feature_set" transaction_id="13" feature="max_children" success="1"></response>

<- feature_get -i 14 -n encoding
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="" command="feature_get" transaction_id="14" feature_name="encoding" supported="1"><![CDATA[iso-8859-1]]></response>

<- feature_get -i 15 -n supports_async
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="" command="feature_get" transaction_id="15" feature_name="supports_async" supported="1"><![CDATA[0]]></response>

<- stdout -i 16 -c 1
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="" command="stdout" transaction_id="16" success="1"></response>

<- stderr -i 17 -c 1
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="" command="stderr" transaction_id="17" success="0"></response>

<- step_into -i 18
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="" command="step_into" transaction_id="18" status="break" reason="ok"><xdebug:message filename="" lineno="14"></xdebug:message></response>

<- stack_get -i 19
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="" command="stack_get" transaction_id="19"><stack where="{main}" level="0" type="file" filename="" lineno="14"></stack></response>

<- stop -i 20
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="" command="stop" transaction_id="20" status="stopped" reason="ok"></response>

-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="" command="stop" transaction_id="20" status="stopping" reason="ok"></response>

Log closed at 2012-02-01 14:08:28

PortQuery reports TCP 9000 & 10000 as LISTENING


Thanks for your help,

Re: xdebug does not stop at breakpoints - hangs at 57% complete [message #875462 is a reply to message #788272] Tue, 22 May 2012 19:41 Go to previous messageGo to next message
Angus Henderson is currently offline Angus HendersonFriend
Messages: 13
Registered: October 2011
Junior Member

Yeah I have the same problem with eclipse PHP and xdebug. I have a recollection of it working earlier on this same project ( cakePHP on a localhost apache2 virtual host )

but i was working on getting the website fully operational and now i cant debug.

I shall try a simpler php project to see if that works next.
Re: xdebug does not stop at breakpoints - hangs at 57% complete [message #878612 is a reply to message #875462] Tue, 29 May 2012 15:53 Go to previous message
Spacesoul blop is currently offline Spacesoul blopFriend
Messages: 9
Registered: April 2012
Junior Member
From my experience with some breakpoints and other Eclipse debugging problems, I would suggest the following:
1. Clear all variables in Watch view.
2. Clear all breakpoints in Breakpoints view.
3. Close firefox and any other browser and app in background which you dont need.
4. In Eclipse preferences, use the internal browser for debugging. It works a lot better than firefox or chrome and catch all breakpoints.
5. Close Eclipse, make sure its not still in memory with process explorer and restart it.
6. Put a first breakpoint on your first index web page, just to check it works.

There are sometimes that Eclipse is not able to follow some functions set at internal libraries or set at very low level may cause a lost session. I would suggest to slowly debug it until the thread is lost or jumped, and manually set the breakpoint in the file before the debugging session is lost. Sothing similar happens in Ollydbg while debugging some internals functions or dlls, that you need to execute them all without stopping it or dive inside it to avoid a lost debug session. Time/session and such type of functions could be hard to follow for the debugger.

[Updated on: Tue, 29 May 2012 15:56]

Report message to a moderator

Previous Topic:How to install fragmented project in Eclipse
Next Topic:xdebug path mapping problem
Goto Forum:

Current Time: Sun Jan 29 13:52:18 GMT 2023

Powered by FUDForum. Page generated in 0.09275 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top