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.
From http://ui.netbeans.org/docs/hi/debugger3.4/overview/index.html#session-management When you start debugging a program, if there is already a session associated with that program that is not running, the IDE will restart the existing session, rather than creating a new session.
What does it mean "session associated with that program that is not running"? I do not understand. Can you reproduce this problem in some current version and describe steps "how to reproduce", please?
wfm
I guess my original wording wasn't very clear. This is an example of what that was mentioning: Start debugging program X Kill/terminate the program (without destroying the session) Start debugging program X again This would just restart the session. It would not create a new one and it would not prompt the user "do you want to create a new session". Put another way, if a particular session is associated with a program, and there is no running program associated with the session, choosing "run in debugger" on the program would act like just like a "restart" command on the session. (none of this is applicable to 3.4 since when a program quits we destroy the session)
David John, You are probably thinking about F4J and IFDEF debugger. We do not have nothing like session without process, and "restart" functionality in NetBeans.
Actually, I wasn't thinking of the ifdef stuff. This was a feature that was intended for 3.4, but didn't make it in. True, it does require having a Restart action. That had also been intended for 3.4, but didn't make it in. This is why I marked this issue as having a target milestone of 4.0. Should I have marked this in some other way? (e.g. marked that it is dependent on the issue saying we need a restart action?)
Well, I'm reopening the issue and leaving it's target milestone as 4.0. I hope that's not bad to do.
Debugger in current NB versions behaves as multisession, restart of existing session does not make sense now.
Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.