| Summary: | Launch without subprocesses and debug targets can terminate by default | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Aleksander Bandelj <aleksander.bandelj> |
| Component: | Debug | Assignee: | JDT-Debug-Inbox <jdt-debug-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | chanskw, darin.eclipse |
| Version: | 3.4 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | stalebug | ||
|
Description
Aleksander Bandelj
If the launch has not contents (process/debug target), even if it can terminate, how do we know the state (terminated vs. not terminated?) Currently, the launch terminated state is based on the terminated state of the things it contains. WTP also has the same problem: Bug 209201 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. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. 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. |