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 90133 - [Study][DB-1] Running multiple debugging sessions accidentally
Summary: [Study][DB-1] Running multiple debugging sessions accidentally
Status: STARTED
Alias: None
Product: debugger
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker with 1 vote (vote)
Assignee: issues@debugger
URL: http://ui.netbeans.org/usability/debu...
Keywords:
: 66652 113760 (view as bug list)
Depends on:
Blocks: 66652
  Show dependency tree
 
Reported: 2006-11-28 08:48 UTC by jrojcek
Modified: 2009-12-10 06:41 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description jrojcek 2006-11-28 08:48:18 UTC 
Finding	
Several participants ran multiple debugging session accidentally. They either hadn't noticed that the 
current session was still running or they expected that the debug project action would restart the 
current session. They ended up with multiple tabs of program output and debugger console in Output 
window which was very confusing.

Severity	
3 participants encountered this problem

Recommendation	
Should we ask the user what to do if there's multiple debugging sessions running: restart the existing 
session or start a new one?
Or maybe introduce an explicit action that would start a new session. The "Run Main Project" would 
always do the restart.
Comment 1 Martin Entlicher 2006-12-02 00:24:55 UTC 
See also issue #66652. IMHO it's a good idea to act like continue instead of
starting a new debugger session for the same thing.
Comment 2 Martin Entlicher 2007-05-17 13:49:05 UTC 
We should resolve this into M10 (till feature freeze).

Originally I thought that a dialog would be a good solution. But not only that I
do not see a handy place in the code where the dialog could be opened at, we
should also consider issue #66652 - specifically I mean:
 1) When program is running, F5 means continue
 2) When program isn't, F5 means start debug

So what if F5 works as proposed above and CTRL-F5 is used then to force to start
a new debug session, despite one is already running?
But then we need two actions, like: "Debug Main Project (CTRL-F5)" and "Debug
Main Project or Continue (F5)".
Then we have also "Debug File (CTRL-SHIFT-F5)". This should probably always
start a new debug session. But if F5 would do continue, after the program
finishes, F5 will start to debug main project, which is strange and unexpected.

Are there any ideas of what can we do about that?
Comment 3 Martin Entlicher 2007-06-14 17:41:13 UTC 
Changing to enhancement and scheduling for the next release.
We did not agree on the solution yet and we would like to make bigger changes in the UI in the next release. Thus this
might be easier to solve then.
Comment 4 Martin Entlicher 2007-08-25 09:56:31 UTC 
*** Issue 113760 has been marked as a duplicate of this issue. ***
Comment 5 Petr Cyhelsky 2008-04-16 15:31:02 UTC 
*** Issue 66652 has been marked as a duplicate of this issue. ***