Community
Participate
Working Groups
Everytime the user resumes a program which quickly exits, a VMDisconnectedException is thrown from the JDI client. When we receive this exception, we either dump it to the console or throw up an error dialog. We should handle this gracefully.
JDIThread now catches the VMDisconnected exception and deals with it gracefully. In addition, the JDIDebugTarget now makes a real distinction between isTerminated and isDisconnected. Finally, JDIModelPresentation has been updated to display "<disconnected>" on JDIDebugTargets which disconnected instead of terminating.
Please verify.
*** Bug 5113 has been marked as a duplicate of this bug. ***
Re-openning
We discussed a re-work of the "disconnect" - it's implementation should be moved up to the JDIDebugElement. There are many cases were we want to handle the disconnect in the same manor.
Fixed as part of 5792.
Verified.