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.
Netbeans release 3.2 build 21 ============================= Steps to reproduce: ------------------- 1. Start session with debugger executor. 2. Attach to this session. 3. Invoke Destroy action on this session. The session will be finished instead of destroyed.
Not a bug. It is feature of JPDA+JDK1.1 debuggers. We can not kill attached process.
It _COULD_ be implemented at least for JPDA debugger see com.sun.jdi.VirtualMachine.exit(int exitCode).
So OK. Sorry for wrong description. But it is REALLY not a bug. See code: finishDebugger () if (debuggerInfo instanceof RemoteDebuggerInfo) virtualMachine.dispose (); else { virtualMachine.exit (0); I realy do not want to kill external processes (we do not have Disconnect action). If you dislike this behaviour start some discussion on nbdev, please...
OK, when you are finishing debugger you should not terminate attached session, but when you are destroying session you should terminate session. From the user's point of view the Destroy action should destroy (e.g. kill) the session - this is what the user expect. If you don't want to kill remote sessions (don't know why - when user is invoking destroy action then he know what he is doing), mark this issue as WONTFIX.
OK. Stop discussing. I agree that current behaviour of Session node properties / actions is not good. I plan to redesign it.