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.
This might be a naive expectation but IDE is there to help me develop my code so here it is: I have a junit test testing my code and it throws an exception - java.util.EmptyStackException. So I thought I will just run it in debugger and debugger will automatically stop at the place which throws the exception and I do Pop Stack couple of times if needed and evaluate the cause in my code. But debugger did not stop. I'm pretty sure will turn this into enhancement issue. But if you look at it from the point of view of modern IDE then unexpected runtime exception will require users attention but IDE did not provide slightest help. Instead it forces user to manually set exception breakpoint and run the test again and once the problem is resolved to remove the breakpoint. Could that be all automated? I guess the problem might be how to detect whether runtime exception is handled by code or not. Because certainly you want to stop only when unhandled runtime exception is thrown.
Thanks David, this is actually already being considered for NB 7.0. See http://wiki.netbeans.org/DebuggerExceptionBP70 It's actually not precisely specified yet, but we'll likely submit a default exception breakpoint for RuntimeExceptions that are not caught. *** This issue has been marked as a duplicate of 144098 ***
Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.