Description Maksim 2010-12-05 04:24:24 EST

Build Identifier: 20100917-0705

In case port 10000 is in use by another application, the PHP Debugger Daemon Thread does not prompt the user about the fact the port is busy. After starting debugging in "Debug As PHP Web Page" mode, the debugger just hangs and the user does not know why.

Another related bug was "Bug 169047 - If port 10000 is already in use - prompt the user". It was decided to overload the method handleMultipleBindingError in DebuggerCommunicationDaemon class relative to its base abstract class - AbstractDebuggerCommunicationDaemon, by adding a proper handling for the problem, but I cannot find these changes fixed in PDT Debugger v0.7 in current version of DebuggerCommunicationDaemon.java (http://dev.eclipse.org/viewcvs/viewvc.cgi/org.eclipse.pdt/plugins/org.eclipse.php.debug.core/src/org/eclipse/php/internal/debug/core/zend/communication/DebuggerCommunicationDaemon.java?view=markup&revision=1.6&root=Tools_Project).

Reproducible: Always

Steps to Reproduce:
1. Open an application that listents to port 10000.
2. Start Eclipse, try debugging script "As PHP Web Page".

Expected result: debugging is started properly, in case debugger encountered some problems when setting up the debug environment, the user is prompted about the potential collisions.
Actual result: if PHP Debugger Daemon Thread cannot be run on port 10000, the user is not notified about the problem.