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.
Summary: | [Study][DB-1] Running multiple debugging sessions accidentally | ||
---|---|---|---|
Product: | debugger | Reporter: | jrojcek <jrojcek> |
Component: | Code | Assignee: | issues@debugger <issues> |
Status: | STARTED --- | ||
Severity: | blocker | CC: | zgursky |
Priority: | P2 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
URL: | http://ui.netbeans.org/usability/debugger_Sep_06/report.html#DB1 | ||
Issue Type: | ENHANCEMENT | Exception Reporter: | |
Bug Depends on: | |||
Bug Blocks: | 66652 |
Description
jrojcek
2006-11-28 08:48:18 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. 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? 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. *** Issue 113760 has been marked as a duplicate of this issue. *** *** Issue 66652 has been marked as a duplicate of this issue. *** |