This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
| Summary: | Finish Action kills session. | ||
|---|---|---|---|
| Product: | debugger | Reporter: | Jan Jancura <jjancura> |
| Component: | Code | Assignee: | issues@debugger <issues> |
| Status: | CLOSED WONTFIX | ||
| Severity: | blocker | CC: | ivan, lhasik, mryzl |
| Priority: | P1 | ||
| Version: | 3.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | TASK | Exception Reporter: | |
|
Description
Jan Jancura
2003-05-06 17:14:20 UTC
In short term we can rename this action to kill. dbx can install some new "finish" action please put me on cc on such issues like this one. Since "Finish" has become "Finish Session" I think this issue can be closed without a fix. We (dbxgui) will implement a TerminateAction (although NB 4.0 should also have this action) for terminating a process in Rainier. Rainier now has fixed "Finish Sessions" so it ends the dbx session. We also have a "Terminate Process" action. We no longer have any short-term requirements for this bug. However, we will need a terminate action in future releases so I'm removing the RAINIER keyword rather than suggesting the bug be closed. Our terminology of "Terminate Process" probably isn't optimal for JPDA debugging. What would be better? Would "Terminate Execution" be better? Or do you think this isn't needed for JPDA debugging? If thats so you can probably close the issue as will-not-fix. IMHO a "Terminate Execution" action is not needed for JPDA debugger, the Finish action just terminates the session (and execution if it's not a remote debugging). Closing as WONTFIX as suggested. Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier. |