I'm using home windows xp x86, wamp, apache2, php 5.3 x86, eclipse php, and xdebug, running on localhost as both a virtualhost as well as an https virtualhost

eclipse version info
Eclipse for PHP Designers Version: Helios Release Build id: 20100617-1415

I'd effectively handled, in some way, to create eclipse and xdebug and all sorts of was well.

I Quickly needed to make an svn branch of my project, and reconfigure apache with 2 new virtual hosts, increase my home windows host files.

Now after i launch debug mode in eclipse everything dies.

Particularly, Basically set no breakpoints the application runs fine, save for that problem I am attempting to debug to begin with.

Basically set a breakpoint, the application stops in the breakpoint, and eclipse seems to become holding the ball. However, after i press continue, or step over, or take on, or sneeze, eclipse informs me execution has started again, however the application is constantly on the hang, and I must restart apache.

I suspect that there's some burglary the communication between eclipse and xdebug, since it looks in my experience like eclipse is delivering my continue or step over command, but xdebug isn't receiving it.

But even when this is the situation I'm not sure how to handle it. Where must i be searching?

Update:
I've effectively had the opportunity to debug using notepad++, its xdebug wordpress plugin, and, just like a caveman, typing &XDEBUG_SESSION_START=session_title in to the url. However, despite my fascination with npp, its debug wordpress plugin is very buggy...

And So I observed an advertisement on stackoverflow for something known as "phpstorm", which professed to become a lightweight yet full featured php ide, with native xdebug support. The demo needed a restart to have it to operate, also it feels type of like focusing on a shaky draft table, however it handled to debug both my small test application and real application very nicely, that is a lot more than I'm able to say for eclipse right now, despite the fact that its most likely my fault.

I most likely must have published this earlier :/ Here's my phpinfo() xdebug section

xdebug

xdebug support  enabled

Version     2.1.

Supported methods Revision

DBGp - Common DeBuGger Protocol     $Revision: 1.145 $

Directive   Local Value Master Value

xdebug.auto_trace   Off Off

xdebug.collect_projects  Off Off

xdebug.collect_includes On  On

xdebug.collect_params

xdebug.collect_return   Off Off

xdebug.collect_vars Off Off

xdebug.default_enable   On  On

xdebug.dump.COOKIE  no value    no value

xdebug.dump.ENV no value    no value

xdebug.dump.FILES   no value    no value

xdebug.dump.GET no value    no value

xdebug.dump.Publish    no value    no value

xdebug.dump.REQUEST no value    no value

xdebug.dump.SERVER  no value    no value

xdebug.dump.SESSION no value    no value

xdebug.dump_globals On  On

xdebug.dump_once    On  On

xdebug.dump_undefined   Off Off

xdebug.extended_info    On  On

xdebug.file_link_format no value    no value

xdebug.idekey   no value    no value

xdebug.manual_url   http://world wide web.php.internet  http://world wide web.php.internet

xdebug.max_nesting_level    100 100

xdebug.overload_var_dump    On  On

xdebug.profiler_aggregate   Off Off

xdebug.profiler_append  Off Off

xdebug.profiler_enable  Off Off

xdebug.profiler_enable_trigger  Off Off

xdebug.profiler_output_dir  C:xampptmp    C:xampptmp

xdebug.profiler_output_title xdebug_profile.%p   xdebug_profile.%p

xdebug.remote_autostart Off Off

xdebug.remote_connect_back  Off Off

xdebug.remote_cookie_expire_time    3600    3600

xdebug.remote_enable    On  On

xdebug.remote_handler   dbgp    dbgp

xdebug.remote_host  localhost   localhost

xdebug.remote_log   c:xamppapachelogsxdebug.log c:xamppapachelogsxdebug.log

xdebug.remote_mode  req req

xdebug.remote_port  9000    9000

xdebug.scream   Off Off

xdebug.show_exception_trace Off Off

xdebug.show_local_vars  Off Off

xdebug.show_mem_delta   Off Off

xdebug.trace_format

xdebug.trace_options

xdebug.trace_output_dir C:xampptmp    C:xampptmp

xdebug.trace_output_title    trace.%c    trace.%c

xdebug.var_displ

 ay_max_children    128 128

 xdebug.var_display_max_data    512 512

 xdebug.var_display_max_depth   3   3

Here's an xdebug log file of after i reproduce the issue

Log opened up at 2011-01-03 08:56:22 ->

<- feature_set -i 33 -n show_hidden -v 1 ->

<- feature_set -i 34 -n max_depth -v 3 ->

<- feature_set -i 35 -n max_children -v 31 ->

<- feature_get -i 36 -n encoding ->

<- feature_get -i 37 -n supports_async ->

<- stdout -i 38 -c 1 ->

<- stderr -i 39 -c 1 ->

<- breakpoint_set -i 40 -t line -f file:///C:%5Cxampp%5Chtdocs%5Clab%5Czf-tutorial%5Cpublic%5Cindex.php -n 21 ->

<- run -i 41 ->

<- stack_get -i 42 ->

<- stack_get -i 43 ->

<- eval -i 44 -- JHRoaXMtPmZpZWxkc1snYm9vbF9jb21wbGV0ZSdd ->

<- eval -i 45 -- JHRoaXMtPnN0YWdlLT5nZXQoJ2Jvb2xfY29tcGxldGUnKQ== ->

<- eval -i 46 -- JHRoaXMtPmZpZWxkc1snYm9vbF9jb21wbGV0ZSdd ->

<- eval -i 47 -- JHRoaXMtPnN0YWdlLT5nZXQoJ2Jvb2xfY29tcGxldGUnKQ== ->

=== breakpoint arrived at, execution breaks. In eclipse I click "step over"

<- step_over -i 48

=== finish of log