Bugzilla – Full Text Bug Listing
| Summary: | Disconnecting from a remote debug session where a packet timeout occurs prevents disconnecting | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | MG <java97301> |
| Component: | Debug | Assignee: | Sarika Sinha <sarika.sinha> |
| Status: | ASSIGNED --- | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | Michael_Rennie |
| Version: | 4.5 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | stalebug | ||
|
Description
MG
We definitely need to do a better job here. Even if the remote debug target has stopped (or we have in any way lost a connection to it) we should be able to gracefully disconnect / stop the debugger to get back into a 'normal' state - without resorting to restarting Eclipse. See the IDisconnect impls in our JDI debug model. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. |