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.
It seems to me that the Stop and Re-run actions in the new output window should somehow be bound to debugging. They are but not in the way I expeted them. 1) As long as a session is running, Re-run is disabled. Re-running is a common deugging activity; why is it disabled? 2) Stop does something, but what? The session seems to still be alive. The Re-run button is enabled. How exatly is state (2) different form state (1)? 3) I Re-run. That starts a new session! I have a suspicion that Stop/Re-run is working at the ant/build level which makes it's conection to any debugging activity indirect and accidental.
These actions come from the build system, thus they are out of programmatic control from debugger modules. Ad 1) I do not own these actions, you would have to ask at "ant" (or "projects"?) component. I guess one is expected to stop it first, then re-run. Ad 2) When the debugged application is suspended, the stop can not do much with it. After you do several more steps or continue the app, the session will terminate. The same problem has Build -> Stop Build/Run. Ad 3) Yes, the old one is supposed to terminate. We need to intercept the stop action somehow and terminate the session via JDI.
This is in fact a duplicate of issue #97748. *** This issue has been marked as a duplicate of 97748 ***
Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.