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 debugging, with a generic breakpoint catching all Exceptions, when the exception happens in an unavailable code, the IDE only changes slightly regarding UI - the continue round button gets activated. If other window than Output is active (e.g. Variables), then there's not much notion of what happened - the output window tab does not get bold or anything - and user might get confused. I suggest that the Debugger Console should pop up. On the other hand, that might irritate people when expecting the exception. So, rather, the Output window tab should appear (not switching to foreground) and flash. Also, (for other RFE), the Output window's tab should get bold when any of it's sub-windows' tabs get bold.
Makes sense. For the Output Window, the bold sub-tabs are the active ones. I'm not sure if this should propagate to the Output window as such. Anyway, this should a RFE for Output window specifically.
Fixed by changeset: 189337:78adc48c0af2 http://hg.netbeans.org/main/rev/78adc48c0af2 When the source code can not be found, Debugger Console is shown with the info about where is the debugger suspended.
Integrated into 'main-golden', will be available in build *201102240001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/78adc48c0af2 User: mentlicher@netbeans.org Log: #195634 Bring attention to the debugger console when execution is suspended at a place where source code is not available.