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.
When I work with two projects I expect the automatic switching between sessions in the case of stopping for breakpoint (switching on the last raised breakpoint). I think this conduct is obvious. SUSE 10.2 NB dev
It's not as obvious as it seems for the first sight. You can be concentrated on watching variable in the first session when another process (thread) stops on another breakpoint and it's not a good idea to switch to there immediately. Also please keep in mind that we can have several debug sessions and several threads in each session. IMO we need to have something like "debugging event monitor" showing where any event (stop at breakpoint, exit, etc.) happens and giving us a possibility to switch to there quickly.
Yes this is good idea. But this monitor is good when exists thread monitor - when I can see which thread (process or session) in which state are, because debugging events are only for debugging and how do they relate to the real processes is hard to understand, I think so.
Real systems - multithreads systems. When IDE don't let developer debug his programs (in realtime with threads) then this IDE only for cartoon-progs :(