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.

Bug 11085

Summary:	Destroy action does not work on remote sessions.
Product:	debugger	Reporter:	Jan Stola <jstola>
Component:	Code	Assignee:	Jan Jancura <jjancura>
Status:	CLOSED WONTFIX
Severity:	blocker
Priority:	P4
Version:	3.x
Hardware:	All
OS:	All
Issue Type:	DEFECT	Exception Reporter:

Description Jan Stola 2001-04-05 10:53:16 UTC

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.

Comment 1 Jan Jancura 2001-04-05 13:24:53 UTC

Not a bug. It is feature of JPDA+JDK1.1 debuggers. We can not kill attached 
process.

Comment 2 Jan Stola 2001-04-05 13:48:29 UTC

It _COULD_ be implemented at least for JPDA debugger
see com.sun.jdi.VirtualMachine.exit(int exitCode).

Comment 3 Jan Jancura 2001-04-05 14:23:09 UTC

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...

Comment 4 Jan Stola 2001-04-05 14:56:02 UTC

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.

Comment 5 Jan Jancura 2001-04-06 15:18:26 UTC

OK. Stop discussing. I agree that current behaviour of Session node properties / 
actions is not good. I plan to redesign it.