Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 169060

Summary:	When connecting to a non-existing debugger or wrong version debugger - no message appears
Product:	z_Archived	Reporter:	Gadi Goldbarg <gadi>
Component:	PDT	Assignee:	Shalom Gibly <shalom>
Status:	CLOSED FIXED	QA Contact:	Gadi Goldbarg <gadi>
Severity:	normal
Priority:	P1	Keywords:	plan
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Gadi Goldbarg

2006-12-26 02:26:41 EST

1. Connect to a remote non-existing debug server
or
2. Connect to a remote servger with debugger version < 5.2.1

The GUI just waits.we don't know what's going on.
Expected - a relevant message.

Comment 1 Shalom Gibly

2007-01-29 11:26:36 EST

Partial fix was implemented. 

We divide this bug into 2 parts. One is dealing with the internal debugger, 
while the other is dealing with the remote debugger (web server).

1. When trying to debug using the internal debugger while the php.ini did not 
direct to a valid debugger, the launch was stuck (forever) in the launches 
view. The fix for this issue is to display an error message when the process 
terminated while we got no debugger response (e.g. no IDebugTarget). In this 
case, we present an error message and remove the launch.

2. When trying to debug using a PHP web server, the situation is a bit more 
complex. The fix for this situation is to keep track on the responses we get 
from the server. In case we do not get any response for a period of 10 seconds, 
we declare a problem and terminate the session. 

For now, I choose not to put this bug as resolved for several reasons:
1. A progress indication should appear while waiting too long for a server 
response. 
2. Ask the user to continue and wait for another period of time, or to 
terminate.
3. (maybe) add a preferences value for the time we wait until we declare a 
problem. 

-SG

Comment 2 Gadi Goldbarg

2007-05-27 10:01:26 EDT

closing this bug